From: David Hildenbrand <david@redhat.com>
To: 李力琼 <liqiong@nfschina.com>, "Greg KH" <gregkh@linuxfoundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mm: fix dereference a null pointer in migrate[_huge]_page_move_mapping()
Date: Thu, 17 Feb 2022 09:56:56 +0100 [thread overview]
Message-ID: <aa1f2e9f-d165-e4a4-d5c3-d285dae4e1a0@redhat.com> (raw)
In-Reply-To: <8f00ecbf-245d-f063-40a3-4aaa77680b73@nfschina.com>
On 17.02.22 09:48, 李力琼 wrote:
> 在 2022/2/17 下午3:51, David Hildenbrand 写道:
>> On 17.02.22 08:29, Greg KH wrote:
>>> On Thu, Feb 17, 2022 at 02:38:08PM +0800, liqiong wrote:
>>>> Upstream has no this bug.
>>> What do you mean by this?
>>>
>>> confused,
>> Dito. If this is fixed upstream and broken in stable kernels, we'd want
>> either a backport of the relevant upstream fix, or if too complicated, a
>> stable-only fix.
>>
>>
> There is a wrong describe， i thought 'Upstream' as the newest code.
> The newest code has no this bug, i should submit this patch to "longterm:4.19".
See https://www.kernel.org/doc/Documentation/process/stable-kernel-rules.rst
Make sure your patch subject starts with something like "[PATCH 4.19
STABLE]" and that your patch targets that stable branch.
Make sure to describe why it doesn't apply to upstream, how it was fixed
upstream, and why we cannot simply backport the upstream way to fix it.
Thanks!
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-02-17 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 6:38 liqiong
2022-02-17 7:29 ` Greg KH
2022-02-17 7:51 ` David Hildenbrand
2022-02-17 8:48 ` 李力琼
2022-02-17 8:56 ` David Hildenbrand [this message]
2022-02-17 7:59 ` 李力琼
2022-02-17 8:39 ` 李力琼
2022-02-17 11:54 ` [PATCH] [PATCH 4.19 STABLE] " liqiong
2022-03-17 10:26 ` Greg KH
2022-03-17 10:27 ` Patch "mm: fix dereference a null pointer in migrate[_huge]_page_move_mapping()" has been added to the 4.19-stable tree gregkh
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=aa1f2e9f-d165-e4a4-d5c3-d285dae4e1a0@redhat.com \
--to=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liqiong@nfschina.com \
--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