[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180711063307.GA31127@infradead.org>
Date: Tue, 10 Jul 2018 23:33:07 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Jann Horn <jannh@...gle.com>
Cc: Christoph Hellwig <hch@...radead.org>, axboe@...nel.dk,
Douglas Gilbert <dgilbert@...erlog.com>,
Al Viro <viro@...iv.linux.org.uk>, fujita.tomonori@....ntt.co.jp,
jejb@...ux.vnet.ibm.com, martin.petersen@...cle.com,
linux-block@...r.kernel.org, linux-scsi@...r.kernel.org,
kernel list <linux-kernel@...r.kernel.org>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>,
security@...nel.org
Subject: Re: [PATCH] sg, bsg: mitigate read/write abuse, block uaccess in
release
On Tue, Jul 10, 2018 at 01:53:02PM -0700, Jann Horn wrote:
> With the error messages like in my sg patch or like with Linus'
> proposed patch (https://lore.kernel.org/lkml/CA+55aFwg-2GP4ASTdd1pusmZkF7c8AN9febVDCaioDxzYJSLfw@mail.gmail.com/)
> applied?
I guess we should follows Linus' suggestions.
Note that he also seems to agree with me to just remove the read/write
interface. Compared to sg bsg really is unused for the read/write
interface. But lets get your fix in first..
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
