Re: Re: Re: [PATCH 2/2] mm, oom: fix potential data corruption when oom_reaper races with writer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michal Hocko wrote:
> On Tue 15-08-17 07:51:02, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> [...]
> > > Were you able to reproduce with other filesystems?
> > 
> > Yes, I can reproduce this problem using both xfs and ext4 on 4.11.11-200.fc25.x86_64
> > on Oracle VM VirtualBox on Windows.
> 
> Just a quick question.
> http://lkml.kernel.org/r/201708112053.FIG52141.tHJSOQFLOFMFOV@xxxxxxxxxxxxxxxxxxx
> mentioned next-20170811 kernel and this one 4.11. Your original report
> as a reply to this thread
> http://lkml.kernel.org/r/201708072228.FAJ09347.tOOVOFFQJSHMFL@xxxxxxxxxxxxxxxxxxx
> mentioned next-20170728. None of them seem to have this fix
> http://lkml.kernel.org/r/20170807113839.16695-3-mhocko@xxxxxxxxxx so let
> me ask again. Have you seen an unexpected content written with that
> patch applied?

No. All non-zero non-0xFF values are without that patch applied.
I want to confirm that that patch actually fixes non-zero non-0xFF values
(so that we can have better patch description for that patch).

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]
  Powered by Linux