lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 9 May 2020 10:24:31 +0200
From:   Christoph Hellwig <>
To:     Ming Lei <>
Cc:     Christoph Hellwig <>, Jens Axboe <>,
        Jim Paris <>, Geoff Levand <>,
        Joshua Morris <>,
        Philip Kelleher <>,
        Minchan Kim <>,
        Nitin Gupta <>,
        Sergey Senozhatsky <>,,,,,,,,,
Subject: Re: remove a few uses of ->queuedata

On Sat, May 09, 2020 at 06:13:21AM +0800, Ming Lei wrote:
> On Fri, May 08, 2020 at 06:15:02PM +0200, Christoph Hellwig wrote:
> > Hi all,
> > 
> > various bio based drivers use queue->queuedata despite already having
> > set up disk->private_data, which can be used just as easily.  This
> > series cleans them up to only use a single private data pointer.
> > 
> > blk-mq based drivers that have code pathes that can't easily get at
> > the gendisk are unaffected by this series.
> Yeah, before adding disk, there still may be requests queued to LLD
> for blk-mq based drivers.
> So are there this similar situation for these bio based drivers?

bio submittsion is based on the gendisk, so we can't submit before
it is added.  The passthrough request based path obviously doesn't apply

Powered by blists - more mailing lists