From: Stefan Priebe <s.priebe@profihost.ag>
To: Kent Overstreet <kmo@daterainc.com>, Jens Axboe <axboe@kernel.dk>
Cc: Arne Wiebalck <Arne.Wiebalck@cern.ch>,
Peter Kieser <peter@kieser.ca>, "eddie@ehuk.net" <eddie@ehuk.net>,
Francis Moreau <francis.moro@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [GIT PULL] bcache changes for 3.17
Date: Fri, 05 Sep 2014 20:46:01 +0200 [thread overview]
Message-ID: <540A04E9.6020606@profihost.ag> (raw)
In-Reply-To: <20140905183301.GB17903@daterainc.com>
Am 05.09.2014 20:33, schrieb Kent Overstreet:
> On Fri, Sep 05, 2014 at 11:10:13AM -0600, Jens Axboe wrote:
>> On 09/05/2014 11:03 AM, Arne Wiebalck wrote:
>>>
>>> On Sep 5, 2014, at 6:41 PM, Peter Kieser <peter@kieser.ca>
>>> wrote:
>>>
>>>>
>>>> On 2014-09-05 8:37 AM, Eddie Chapman wrote:
>>>>> On 05/09/14 15:17, Jens Axboe wrote:
>>>>>> (from oldest to newest). And that's just from 3.16 to 3.17-rc3, going
>>>>>> all the way back to 3.10 would be a lot of work. If there's anyone that
>>>>>> cares about bcache on stable kernels (and actually use it), now would be
>>>>>> a good time to pipe up.
>>>>>
>>>>> Just "piping up" as I care about bcache and actually use it in production on 3.10! Shame I don't have the knowledge to try and backport these though :-)
>>>>>
>>>>> Eddie
>>>>
>>>> I'm "piping up" as well, I use bcache on 3.10 in production.
>>>>
>>>> -Peter
>>>>
>>>
>>>
>>> More "piping up": we currently use bcache on a few nodes in production, on 3.14 and 3.15, and plan to roll it out on a wider scale now.
>>> If necessary we'll go with these kernels, but we'd certainly prefer our usual 3.10-based CentOS kernel.
>>
>> OK, so we definitely have people using it in production. My concern was
>> that whomever does the backport of the appropriate patches to 3.10/14/15
>> stable would have an audience for getting some amount of testing of such
>> a patch series.
>>
>> Now we just need someone to line up to do the work...
>
> I can try and make some time for backporting; if we've got people lined up for
> testing that will help a lot.
>
> Backporting fixes to 3.10 will be harder, but if memory serves there hasn't been
> as much churn since 3.14 so backporting fixes to then shouldn't be too bad. If
> Stefan wants to post what he's got for 3.10 though I can try and backport some
> more fixes on top of that, though
You'll find them here:
https://github.com/profihost/linux-stable/commits/bcache_latest_fixes
Most probably you don't want the last four.
Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-09-05 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 4:33 [GIT PULL] bcache changes for 3.17 Kent Overstreet
2014-08-05 16:58 ` Jens Axboe
2014-08-10 7:54 ` Peter Kieser
2014-09-05 7:31 ` Francis Moreau
2014-09-05 14:17 ` Jens Axboe
2014-09-05 14:28 ` Vasiliy Tolstov
2014-09-05 14:30 ` Jens Axboe
2014-09-05 14:44 ` Francis Moreau
2014-09-05 21:46 ` Greg KH
2014-09-05 15:37 ` Eddie Chapman
2014-09-05 16:41 ` Peter Kieser
2014-09-05 17:03 ` Arne Wiebalck
2014-09-05 17:10 ` Jens Axboe
2014-09-05 18:33 ` Kent Overstreet
2014-09-05 18:46 ` Stefan Priebe [this message]
2015-02-05 13:40 ` Francis Moreau
2014-09-06 0:33 ` Chuck Ebbert
2014-09-05 21:45 ` Greg KH
2014-09-05 22:21 ` Jens Axboe
2014-09-08 15:26 ` Greg KH
2014-09-05 23:17 ` Peter Kieser
2014-09-08 15:27 ` Greg KH
2014-09-06 9:23 ` Francis Moreau
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=540A04E9.6020606@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=Arne.Wiebalck@cern.ch \
--cc=axboe@kernel.dk \
--cc=eddie@ehuk.net \
--cc=francis.moro@gmail.com \
--cc=kmo@daterainc.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@kieser.ca \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).