Re: [stable] binder: fix race between munmap() and direct reclaim

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

 



On Tue, Jun 4, 2019 at 7:50 AM Greg Kroah-Hartman
<gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>
> On Fri, May 31, 2019 at 01:09:53PM -0700, Todd Kjos wrote:
> > Greg,
> >
> > I'm really confused. [1] was my submittal to stable for "binder: fix
> > race between munmap() and direct reclaim" which I think looks correct.
> >
> > For "binder: fix handling of misaligned binder object", I only
> > submitted to LKML [2]. But then I see [3] for 4.14 (that looks
> > incorrect as Ben pointed out).
> >
> > So the result is that fix is present in the LTS trees where it is
> > needed, but it has the wrong commit message and headline.
> >
> > I agree with Ben that the cleanest approach is to revert and apply the
> > correct version (to 4.14, 4.19, 5.0). I think the correct version is
> > the one I sent [1], but please let me know if you see something I
> > screwed up or if you need me to do something.
> >
> > [1] https://www.spinics.net/lists/stable/msg299033.html
> > [2] https://lkml.org/lkml/2019/2/14/1235
> > [3] https://lkml.org/lkml/2019/4/30/650
>
> Can you send me a patch series that fixes things up properly?  I really
> don't know exactly what to do here, sorry.

Sent. 2 patches for each of 4.14, 4.19, 5.0 (1/2=revert of bad patch,
2/2 apply good patch). Code ends up the same.

-Todd



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux