linux-kernel - Re: [PULL] Re: bcache stability patches

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] [day] [month] [year] [list]

Date:	Thu, 7 Jan 2016 18:02:51 -0800 (PST)
From:	Eric Wheeler <bcache@...ts.ewheeler.net>
To:	Jens Axboe <axboe@...nel.dk>
cc:	Kent Overstreet <kent.overstreet@...il.com>,
	Eric Wheeler <bcache@...ts.ewheeler.net>,
	Al Viro <viro@...iv.linux.org.uk>,
	Denis Bychkov <manover@...il.com>, g2p.code@...il.com,
	Jiri Kosina <jkosina@...e.com>,
	Joshua Schmid <jschmid@...e.com>, linux-bcache@...r.kernel.org,
	linux-kernel@...r.kernel.org, stefan.bader@...onical.com,
	Takashi Iwai <tiwai@...e.de>,
	Vojtech Pavlik <vojtech@...e.com>,
	Zheng Liu <gnehzuil.liu@...il.com>,
	Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [PULL] Re: bcache stability patches

On Wed, 30 Dec 2015, Jens Axboe wrote:

> On 12/30/2015 08:15 PM, Kent Overstreet wrote:
> > On Wed, Dec 30, 2015 at 10:59:39AM -0700, Jens Axboe wrote:
> > > Looking over these, most are really simple one-liners, and nothing sticks
> > > out as being overly complicated. Kent, do you have any plans to maintain
> > > the
> > > in-kernel bcache?
> >
> > Yeah - these patches are all fine, go ahead and pull.
> 
> Great, thanks.
> 
> > I may start doing maintainence again at some point (but if there's someone
> > willing to step up and take over and do a good job of it, I'd gladly hand
> > things
> > off)

We use this in production internally, so I'll keep collecting patches and 
may ask for pulls from time to time.  

> As long as we have a path into mainline for stability fixes, at least that's
> better than before.
> 
> Thanks Eric for collecting these. I've reformatted some of them a bit, not
> sure if that's github crappery, or if they came like that. It's pushed out
> now.

You're welcome.  It could be github crappery, however, these were 
copy-pasted and cleaned up in various ways such that they merge into 
3.17-rc1 and then merge forward into 4.1.15 which we build against---so 
who knows about formatting, whitspace, and other minor issues.  I'm just 
glad they are on their way to 4.5 with stable@ Cc's!

BTW, can someone suggest an alternate git host with less crappery?

-Eric

> 
> -- 
> Jens Axboe
> 
> 
>