All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Eric Wheeler <bcache@lists.ewheeler.net>,
	Kent Overstreet <kent.overstreet@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	Denis Bychkov <manover@gmail.com>,
	g2p.code@gmail.com, Jiri Kosina <jkosina@suse.com>,
	Joshua Schmid <jschmid@suse.com>,
	linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
	stefan.bader@canonical.com, Takashi Iwai <tiwai@suse.de>,
	Vojtech Pavlik <vojtech@suse.com>,
	Zheng Liu <gnehzuil.liu@gmail.com>,
	Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [PULL] Re: bcache stability patches
Date: Wed, 30 Dec 2015 10:59:39 -0700	[thread overview]
Message-ID: <56841B8B.6070306@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.11.1512291807510.30746@mail.ewheeler.net>

On 12/29/2015 08:00 PM, Eric Wheeler wrote:
> Hi Jens and Kent,
>
> This affects many users, so please take a look when you have a moment:
>
> There is a growing bcache user community with a well-tested patchset that
> is necessary for production bcache use.  The diffstat is small and we all
> want someone to pull it in and get it into mainline.  This would serve
> many people if this can get pulled in upstream.
>
> More below:
>
> On Tue, 22 Dec 2015, Denis Bychkov wrote:
>> There is a set of bcache stability patches elevating bcache stability to
>> production level. As far as I know, there is no single reported and peer
>> confirmed bug that is not solved by this set. Unfortunately, for some
>> reason, Kent does not have enough time and/or energy to review them and
>> send them upstream. Let's come up with a solution that would allow to
>> review all these patches (some of them written by Ken himself, some of
>> them produced by the community), review them and hand them to the
>> maintainer who is willing to apply them upstream. Without that, bcache
>> is just another half-assed unstable and buggy cache layer. These patches
>> will allow people to start use bcache in production systems. Please find
>> the patch set attached. (The patches apply cleanly to 4.3 and 4.4 kernel
>> series).
>
> Hi Dennis,
>
> I'm maintaining a branch here that is ready to merge.  We have been
> testing this for about a year in production and works great.  All Cc's and
> authors are correct and it (should) have every stability patch below,
> possibly others too.  Please tell me if there are any patches missing:
>
> git pull https://github.com/ewheelerinc/linux.git bcache-patches-for-3.17
> (Yes, github for hosting only, I don't edit with their web interfaces.)
>
> Note that this branch still merges cleanly through v4.4-rc7 and as far
> back as 3.17-rc1 (maybe earlier).  Each patch provides Cc: stable@vger.kernel.org.
>
> It is ready to merge!  We just need Jens or Kent or someone to pull it in.
> Here is the diffstat and shortlog against v4.4-rc7:
>
>   drivers/md/bcache/btree.c     |  5 ++++-
>   drivers/md/bcache/super.c     | 16 ++++++++++++----
>   drivers/md/bcache/writeback.c | 37 ++++++++++++++++++++++++++++++-------
>   drivers/md/bcache/writeback.h |  3 ++-
>   4 files changed, 48 insertions(+), 13 deletions(-)
>
> Al Viro (1):
>        bcache: fix a leak in bch_cached_dev_run()
>
> Gabriel de Perthuis (1):
>        bcache: allows use of register in udev to avoid "device_busy" error.
>
> Kent Overstreet (2):
>        bcache: Add a cond_resched() call to gc
>        bcache: Change refill_dirty() to always scan entire disk if
> necessary
>
> Stefan Bader (1):
>        bcache: prevent crash on changing writeback_running
>
> Zheng Liu (3):
>        bcache: fix a livelock when we cause a huge number of cache misses
>        bcache: clear BCACHE_DEV_UNLINK_DONE flag when attaching a backing device
>        bcache: unregister reboot notifier if bcache fails to unregister device

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?

If I don't hear otherwise, I'll pull these in for 4.5.

-- 
Jens Axboe

  reply	other threads:[~2015-12-30 17:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  9:13 BCACHE stability patches Denis Bychkov
2015-12-22  9:13 ` Denis Bychkov
2015-12-30  3:00 ` [PULL] Re: bcache " Eric Wheeler
2015-12-30  3:00   ` Eric Wheeler
2015-12-30 17:59   ` Jens Axboe [this message]
2015-12-31  3:15     ` Kent Overstreet
2015-12-31  3:25       ` Jens Axboe
2015-12-31  5:18         ` Kent Overstreet
2015-12-31 21:19           ` Denis Bychkov
2016-01-01 22:36             ` Kent Overstreet
2016-01-02  1:28               ` Denis Bychkov
2016-01-02 11:50                 ` Vojtech Pavlik
2016-01-02 15:48                   ` Denis Bychkov
2016-01-03  0:12                     ` Kent Overstreet
2016-01-08  2:02         ` Eric Wheeler
2016-02-24  6:45         ` bcache stability patches: Now mainlined! Eric Wheeler
2016-02-24  6:57           ` Stefan Priebe - Profihost AG
2016-02-24  7:34             ` Eric Wheeler
2016-02-24  8:57           ` Tim Small
2015-12-31  7:23   ` [PULL] Re: bcache stability patches Denis Bychkov

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=56841B8B.6070306@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bcache@lists.ewheeler.net \
    --cc=g2p.code@gmail.com \
    --cc=gnehzuil.liu@gmail.com \
    --cc=jkosina@suse.com \
    --cc=jschmid@suse.com \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manover@gmail.com \
    --cc=stefan.bader@canonical.com \
    --cc=tiwai@suse.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vojtech@suse.com \
    --cc=wenqing.lz@taobao.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.