All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Shixin <liushixin2@huawei.com>
To: Suren Baghdasaryan <surenb@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>, <stable@vger.kernel.org>,
	"Jann Horn," <jannh@google.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: Questions about backports of fixes for "CoW after fork() issue"
Date: Wed, 16 Jun 2021 17:28:54 +0800	[thread overview]
Message-ID: <add3f456-052e-6f40-2949-0685b563fdee@huawei.com> (raw)
In-Reply-To: <CAJuCfpG8p7AasufvqehNOLdoXw5ZQFuQhi6mhqPvA3GbPn1puQ@mail.gmail.com>

On 2021/6/16 15:11, Suren Baghdasaryan wrote:
> On Tue, Jun 15, 2021 at 11:52 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>> On Wed, Jun 16, 2021 at 02:47:15PM +0800, Liu Shixin wrote:
>>> Hi, Suren,
>>>
>>> I read the previous discussion about fixing CVE-2020-29374 in stable 4.14 and 4.19 in
>>> <https://lore.kernel.org/linux-mm/20210401181741.168763-1-surenb@google.com/>
>>>
>>> https://lore.kernel.org/linux-mm/20210401181741.168763-1-surenb@google.com/
>>>
>>> And the results of the discussion is that you backports of 17839856fd58 for 4.14 and
>>>
>>> 4.19 kernels.
>>>
>>> But the bug about dax and strace in the discussion has not been solved, right? I don't
>>>
>>> find a conclusion on this issue, am I missing something? Does this problem still exist in
>>>
>>> the stable 4.14 and 4.19 kernel?
> That is my understanding after discussions with Andrea but I did not
> verify that myself. As Greg pointed out, the best way would be to try
> it out.
> Thanks,
> Suren.
>
>> As the code is all there for you, can you just test them and see for
>> yourself?
>>
>> thanks,
>>
>> greg k-h
> .
>
Thank you both for replies. I have tested it in stable 4.19 kernel and the bug is existed as expected.

Thanks,
Liu Shixin

  reply	other threads:[~2021-06-16  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f546c93e-0e36-03a1-fb08-67f46c83d2e7@huawei.com>
2021-06-16  6:52 ` Questions about backports of fixes for "CoW after fork() issue" Greg Kroah-Hartman
2021-06-16  7:11   ` Suren Baghdasaryan
2021-06-16  9:28     ` Liu Shixin [this message]
2021-06-16  9:36       ` Greg Kroah-Hartman
2021-06-16 10:17         ` Vlastimil Babka

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=add3f456-052e-6f40-2949-0685b563fdee@huawei.com \
    --to=liushixin2@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=mpatocka@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    /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.