linux-kernel - Re: [PULL] bcache: multiple updates

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <20161030140050.q6ywphi3by6yoczc@kmo-pixel>
Date:   Sun, 30 Oct 2016 06:00:50 -0800
From:   Kent Overstreet <kent.overstreet@...il.com>
To:     Eric Wheeler <bcache@...ts.ewheeler.net>
Cc:     Jens Axboe <axboe@...nel.dk>, linux-bcache@...r.kernel.org,
        dave@...olabs.net, linux-kernel@...r.kernel.org,
        Kai Krakow <kai@...shome.de>,
        Wido den Hollander <wido@...odh.nl>
Subject: Re: [PULL] bcache: multiple updates

On Sat, Oct 29, 2016 at 06:32:38PM -0700, Eric Wheeler wrote:
> On Thu, 27 Oct 2016, Jens Axboe wrote:
> 
> > On 10/27/2016 05:27 PM, Eric Wheeler wrote:
> > > Hi Jens,
> > >
> > > Please pull this v4.9-rc2 based series of bcache updates for v4.9-rc3:
> > > (You may disregard the previous -rc1-based request.)
> > >
> > >   git pull https://bitbucket.org/ewheelerinc/linux.git
> > >   v4.9-rc2-bcache-updates
> > >
> > > Thank you!
> > >
> > > --
> > > Eric Wheeler
> > >
> > > ]# git log --oneline v4.9-rc2..HEAD
> > > bd532a6 bcache: partition support: add 16 minors per bcacheN device
> > > 3312845 bcache: Make gc wakeup sane, remove set_task_state()
> > > 6bb7f1e bcache: update bio->bi_opf bypass/writeback REQ_ flag hints
> > > 3d58a09 bcache: documentation for ioprio cache hinting
> > > 2e8884b bcache: introduce per-process ioprio-based bypass/writeback hints
> > 
> > How many of these are applicable to 4.9-rc3? I took a quick look at
> > them, and some of them look like they should go into the 4.10 branch
> > instead. We're after the merge window, so only strict fixes. Cleanups
> > and no features, no go.
> 
> 3312845 might need to be in 4.9.  Not sure, kent asked me to pick it up in 
> my next pull request.  4.10 is fine for the rest.
> 
> Kent, Davidlohr, does 3312845 need to land in 4.9 for some reason?

No, that can wait until 4.10.