[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <26c12f13870a2276f41aebfea6e467d576f70860.camel@HansenPartnership.com>
Date: Thu, 02 Sep 2021 16:23:43 -0700
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Jens Axboe <axboe@...nel.dk>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [GIT PULL] first round of SCSI updates for the 5.14+ merge
window
On Thu, 2021-09-02 at 15:38 -0700, Linus Torvalds wrote:
> On Thu, Sep 2, 2021 at 9:50 AM James Bottomley
> <James.Bottomley@...senpartnership.com> wrote:
> > We also picked up a non trivial conflict with the already upstream
> > block tree in st.c
>
> Hmm. Resolving that conflict, I just reacted to how the st.c code
> passes in a NULL gendisk to scsi_ioctl() and then on to
> blk_execute_rq().
>
> Just checking that was fine, and I notice how *many* places do that.
>
> Should the blk_execute_rq() function even take that "struct gendisk
> *bd_disk" argument at all?
>
> Maybe the right thing to do would be for the people who care to just
> set rq->rq_disk before starting the request..
>
> But I guess it's traditional, and nobody cares.
It's certainly traditional, but Christoph has been caring a lot about
cleaning up our gendisks recently, so he might be interested in seeing
if he can fix it ...
James
Powered by blists - more mailing lists