From: Jens Axboe <axboe@kernel.dk>
To: Sasha Levin <sashal@kernel.org>, gregkh@linuxfoundation.org
Cc: hch@lst.de, bvanassche@acm.org, jack@suse.cz, yuyufen@huawei.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] bdi: add a ->dev_name field to struct backing_dev_info" failed to apply to 5.6-stable tree
Date: Tue, 12 May 2020 09:10:08 -0600 [thread overview]
Message-ID: <bccfa4fa-33e7-cec8-0a05-994e09e5629d@kernel.dk> (raw)
In-Reply-To: <20200512143851.GQ13035@sasha-vm>
On 5/12/20 8:38 AM, Sasha Levin wrote:
> On Tue, May 12, 2020 at 01:51:12PM +0200, gregkh@linuxfoundation.org wrote:
>>
>> The patch below does not apply to the 5.6-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>.
>>
>> thanks,
>>
>> greg k-h
>>
>> ------------------ original commit in Linus's tree ------------------
>>
>>From 6bd87eec23cbc9ed222bed0f5b5b02bf300e9a8d Mon Sep 17 00:00:00 2001
>> From: Christoph Hellwig <hch@lst.de>
>> Date: Mon, 4 May 2020 14:47:56 +0200
>> Subject: [PATCH] bdi: add a ->dev_name field to struct backing_dev_info
>>
>> Cache a copy of the name for the life time of the backing_dev_info
>> structure so that we can reference it even after unregistering.
>>
>> Fixes: 68f23b89067f ("memcg: fix a crash in wb_workfn when a device disappears")
>> Reported-by: Yufen Yu <yuyufen@huawei.com>
>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>> Reviewed-by: Jan Kara <jack@suse.cz>
>> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>
> I've also grabbed eb7ae5e06bb6 ("bdi: move bdi_dev_name out of line") as
> a dependency and queued both for 5.6 and 5.4.
Thanks Sasha!
--
Jens Axboe
prev parent reply other threads:[~2020-05-12 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 11:51 FAILED: patch "[PATCH] bdi: add a ->dev_name field to struct backing_dev_info" failed to apply to 5.6-stable tree gregkh
2020-05-12 14:38 ` Sasha Levin
2020-05-12 15:10 ` Jens Axboe [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=bccfa4fa-33e7-cec8-0a05-994e09e5629d@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yuyufen@huawei.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.