From: Greg KH <gregkh@linuxfoundation.org>
To: dsterba@suse.cz, Sasha Levin <Alexander.Levin@microsoft.com>,
Liu Bo <bo.liu@linux.alibaba.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] Btrfs: fix NULL pointer dereference in log_dir_items
Date: Thu, 5 Apr 2018 21:16:48 +0200 [thread overview]
Message-ID: <20180405191648.GB19589@kroah.com> (raw)
In-Reply-To: <20180405171114.GL2635@twin.jikos.cz>
On Thu, Apr 05, 2018 at 07:11:14PM +0200, David Sterba wrote:
> On Thu, Apr 05, 2018 at 04:42:34PM +0000, Sasha Levin wrote:
> > Hi.
> >
> > [This is an automated email]
> >
> > This commit has been processed by the -stable helper bot and determined
> > to be a high probability candidate for -stable trees. (score: 9.9156)
> >
> > The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
> >
> > v4.15.15: Build OK!
> > v4.14.32: Build OK!
> > v4.9.92: Build OK!
> > v4.4.126: Build OK!
> >
> > Please let us know if you'd like to have this patch included in a stable tree.
>
> Yes, in this case we expect that the Fixes: tag will let the patch flow
> to stable after it gets applied to master.
Fixes: tags almost never cause that to happen, unless I am bored and go
digging for them.
Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly if you want a patch applied to the stable
tree.
thanks,
greg k-h
prev parent reply other threads:[~2018-04-05 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1522691988-127156-1-git-send-email-bo.liu@linux.alibaba.com>
2018-04-05 16:42 ` [PATCH v2] Btrfs: fix NULL pointer dereference in log_dir_items Sasha Levin
2018-04-05 17:11 ` David Sterba
2018-04-05 17:21 ` Sasha Levin
2018-04-05 19:16 ` 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=20180405191648.GB19589@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=bo.liu@linux.alibaba.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.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