[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez0Ps6ib=8_fGJbdk7w--7MNkhkvE1PG6hk=fJ=ZoEtFNQ@mail.gmail.com>
Date: Thu, 21 Jun 2018 14:54:05 +0200
From: Jann Horn <jannh@...gle.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: axboe@...nel.dk, fujita.tomonori@....ntt.co.jp, dgilbert@...erlog.com,
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>, Al Viro <viro@...iv.linux.org.uk>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>, security@...nel.org
Subject: Re: [PATCH] sg, bsg: mitigate read/write abuse, block uaccess in release
On Thu, Jun 21, 2018 at 2:40 PM Christoph Hellwig <hch@...radead.org> wrote:
> Can you resend a patch for the sg driver alone?
Okay, will do.
> Also I think
> we just want the scsi_safe_file_access code inside sg itself,
> it really has nothing to do with the reset of the contents in
> scsi_cmnd.h
Okay. (I put it there because I couldn't figure out a better common
header and didn't want to create two new copies of the code.)
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.
