* Re: Questions about backports of fixes for "CoW after fork() issue" [not found] <f546c93e-0e36-03a1-fb08-67f46c83d2e7@huawei.com> @ 2021-06-16 6:52 ` Greg Kroah-Hartman 2021-06-16 7:11 ` Suren Baghdasaryan 0 siblings, 1 reply; 5+ messages in thread From: Greg Kroah-Hartman @ 2021-06-16 6:52 UTC (permalink / raw) To: Liu Shixin Cc: Suren Baghdasaryan, Vlastimil Babka, stable, Jann Horn,, Mikulas Patocka 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? As the code is all there for you, can you just test them and see for yourself? thanks, greg k-h ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Questions about backports of fixes for "CoW after fork() issue" 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 0 siblings, 1 reply; 5+ messages in thread From: Suren Baghdasaryan @ 2021-06-16 7:11 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: Liu Shixin, Vlastimil Babka, stable, Jann Horn,, Mikulas Patocka 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Questions about backports of fixes for "CoW after fork() issue" 2021-06-16 7:11 ` Suren Baghdasaryan @ 2021-06-16 9:28 ` Liu Shixin 2021-06-16 9:36 ` Greg Kroah-Hartman 0 siblings, 1 reply; 5+ messages in thread From: Liu Shixin @ 2021-06-16 9:28 UTC (permalink / raw) To: Suren Baghdasaryan, Greg Kroah-Hartman Cc: Vlastimil Babka, stable, Jann Horn,, Mikulas Patocka 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Questions about backports of fixes for "CoW after fork() issue" 2021-06-16 9:28 ` Liu Shixin @ 2021-06-16 9:36 ` Greg Kroah-Hartman 2021-06-16 10:17 ` Vlastimil Babka 0 siblings, 1 reply; 5+ messages in thread From: Greg Kroah-Hartman @ 2021-06-16 9:36 UTC (permalink / raw) To: Liu Shixin Cc: Suren Baghdasaryan, Vlastimil Babka, stable, Jann Horn,, Mikulas Patocka On Wed, Jun 16, 2021 at 05:28:54PM +0800, Liu Shixin wrote: > 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. Great, can you provide a working backport of the patches needed to solve this for 4.19 so that we can apply them? thanks, greg k-h ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Questions about backports of fixes for "CoW after fork() issue" 2021-06-16 9:36 ` Greg Kroah-Hartman @ 2021-06-16 10:17 ` Vlastimil Babka 0 siblings, 0 replies; 5+ messages in thread From: Vlastimil Babka @ 2021-06-16 10:17 UTC (permalink / raw) To: Greg Kroah-Hartman, Liu Shixin, Linus Torvalds Cc: Suren Baghdasaryan, stable, Jann Horn,, Mikulas Patocka On 6/16/21 11:36 AM, Greg Kroah-Hartman wrote: > On Wed, Jun 16, 2021 at 05:28:54PM +0800, Liu Shixin wrote: >> 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. If you can reproduce it, great. That means a root cause can be found and fixed, hopefully in a minimal way. > Great, can you provide a working backport of the patches needed to solve > this for 4.19 so that we can apply them? We probably don't want to blindly backport the upstream patches (that also fixed dax+ptrace as a side-effect) because they changed the semantics a lot and led to further fixes, which is IMHO too risky to do now in stable. Linus also thought so: https://lore.kernel.org/linux-mm/CAHk-=whUKYdWbKfFzXXnK8n04oCMwEgSnG8Y3tgE=YZUjiDvbA@mail.gmail.com/#t > thanks, > > greg k-h > ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-06-16 10:17 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [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 2021-06-16 9:36 ` Greg Kroah-Hartman 2021-06-16 10:17 ` Vlastimil Babka
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.