From: Greg KH <greg@kroah.com>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: Sasha Levin <sashal@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 5.4-stable request: 52e29e331070cd ('btrfs: don't set path->leave_spinning for truncate')
Date: Thu, 27 Feb 2020 10:21:42 +0100 [thread overview]
Message-ID: <20200227092142.GA520306@kroah.com> (raw)
In-Reply-To: <b7e8d6da-087a-b7e4-7be2-8a9a6ef1e9a1@applied-asynchrony.com>
On Thu, Feb 20, 2020 at 04:12:24PM +0100, Holger Hoffstätte wrote:
>
> Hi Sasha,
>
> On 2/18/20 5:14 PM, Sasha Levin wrote:
> > On Tue, Feb 18, 2020 at 01:01:40PM +0100, Holger Hoffstätte wrote:
> > > Hi,
> > >
> > > I was just looking throught the current 5.4-stable queue and saw that
> > > 28553fa992cb28 ('Btrfs: fix race between shrinking truncate and fiemap')
> > > is queued. Upstream has a follow-up fix for this: 52e29e331070cd aka
> > > 'btrfs: don't set path->leave_spinning for truncate'.
> > >
> > > Would be nice to get those in together. I only looked at 5.4, don't
> > > know about other queues.
> >
> > Since that fix just hit upstream, I'm going to remove 28553fa992cb28
> > from the queue now and work on getting both patches in the next release.
>
> Thanks, but maybe wait until [1] has also hit mainline? It's another fix
> for 28553fa992cb28.
>
> thanks,
> Holger
>
> [1] https://patchwork.kernel.org/patch/11394171/
Ok, I think I have this all now queued up properly for 5.4.y and 5.5.y,
but older kernels will need backports. Can someone send those series of
patches to stable@vger.kernel.org if it is needed in older kernels like
the commit says they are needed?
thanks,
greg k-h
prev parent reply other threads:[~2020-02-27 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 12:01 5.4-stable request: 52e29e331070cd ('btrfs: don't set path->leave_spinning for truncate') Holger Hoffstätte
2020-02-18 16:14 ` Sasha Levin
2020-02-20 15:12 ` Holger Hoffstätte
2020-02-27 9:21 ` Greg KH [this message]
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=20200227092142.GA520306@kroah.com \
--to=greg@kroah.com \
--cc=holger@applied-asynchrony.com \
--cc=sashal@kernel.org \
--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).