From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>, Chris Mason <clm@fb.com>,
Jan Kara <jack@suse.cz>, stable <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] writeback: fix use-after-free in finish_writeback_work()" failed to apply to 5.3-stable tree
Date: Mon, 14 Oct 2019 08:40:34 -0700 [thread overview]
Message-ID: <20191014154034.GE18794@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <CAHk-=wiE8oFcPHCMM11j0svKQWwM8nuhnQ9R1OdLbfum5ALvOg@mail.gmail.com>
On Sat, Oct 12, 2019 at 02:54:26PM -0700, Linus Torvalds wrote:
> On Sat, Oct 12, 2019 at 1:18 AM <gregkh@linuxfoundation.org> wrote:
> >
> > The patch below does not apply to the 5.3-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> Hmm. It looks to me like 5.3 doesn't have the use-after-free problem,
> and that it was introduced by 5b9cce4c7eb0696558 ("writeback:
> Generalize and expose wb_completion")
>
> So I think the "Fixes" tag is right, and the "Cc: stable" is wrong.
Yeap, sorry about that. I think I forgot --contains when running
git-describe and mindlessly copied the output.
Thanks.
--
tejun
prev parent reply other threads:[~2019-10-14 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 8:17 FAILED: patch "[PATCH] writeback: fix use-after-free in finish_writeback_work()" failed to apply to 5.3-stable tree gregkh
2019-10-12 14:34 ` Sasha Levin
2019-10-12 21:54 ` Linus Torvalds
2019-10-14 15:40 ` Tejun Heo [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=20191014154034.GE18794@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).