linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jann Horn <jannh@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi@vger.kernel.org,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] SCSI fixes for 4.18-rc3
Date: Mon, 16 Jul 2018 18:20:35 +0200	[thread overview]
Message-ID: <CAG48ez0h4c7z+a6Dj-94Wb4-HdWM1YbrBd44oyBEiQyu8NhCKA@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwg-2GP4ASTdd1pusmZkF7c8AN9febVDCaioDxzYJSLfw@mail.gmail.com>

On Tue, Jul 10, 2018 at 2:41 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Fri, Jul 6, 2018 at 10:22 PM James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > We did discuss removing the r/w interface, but, as you say, it's been
> > around for ages so it's not clear what regressions would surface if we
> > did.
>
> So since nobody else followed up on this, the attached patch is what I
> was thinking of just committing.
>
> It removes the warnings from the access check, and just puts them
> (unconditionally) at the top of the read/write function instead.

Minor issue:

+ pr_err_once("process %d (%s) does direct read on /dev/sg",
+ task_tgid_vnr(current), current->comm);
[...]
+ pr_err_once("process %d (%s) does direct write on /dev/sg",
+ task_tgid_vnr(current), current->comm);

printk wants a newline at the end of the message, otherwise the
message hangs until the next message is printed.

  parent reply	other threads:[~2018-07-16 16:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 21:38 [GIT PULL] SCSI fixes for 4.18-rc3 James Bottomley
2018-07-07  2:31 ` Linus Torvalds
2018-07-07  2:39   ` Linus Torvalds
2018-07-07  2:48     ` Linus Torvalds
2018-07-07  5:22       ` James Bottomley
2018-07-10  0:41         ` Linus Torvalds
2018-07-10 17:36           ` Jann Horn
2018-07-10 17:49             ` Linus Torvalds
2018-07-10 18:04               ` Linus Torvalds
2018-07-10 21:53           ` Tony Battersby
2018-07-10 22:24             ` Linus Torvalds
2018-07-11  0:40               ` Linus Torvalds
2018-07-11  6:45             ` Christoph Hellwig
2018-07-11 13:56               ` Tony Battersby
2018-07-16 16:20           ` Jann Horn [this message]
2018-07-07  3:08     ` Jann Horn
2018-07-07  3:25       ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAG48ez0h4c7z+a6Dj-94Wb4-HdWM1YbrBd44oyBEiQyu8NhCKA@mail.gmail.com \
    --to=jannh@google.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).