Re: [mm/page_alloc or mm/vmscan or mm/zswap] use-after-free in obj_malloc()

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

 



On (24/02/23 13:56), Sergey Senozhatsky wrote:
> On (24/02/22 20:50), Yosry Ahmed wrote:
> > On Thu, Feb 22, 2024 at 8:48 PM Sergey Senozhatsky
> > <senozhatsky@xxxxxxxxxxxx> wrote:
> > >
> > > On (24/02/22 18:27), Yosry Ahmed wrote:
> > > > I also don't see any recent changes in mm/zsmalloc.c that modify this
> > > > code, so maybe it wasn't introduce in 6.7. I will defer to Minchan and
> > > > Sergey, I don't think zswap is an active actor in this bug report.
> > >
> > > Yeah. [1] are the only recent zsmalloc patches I can recall, and those
> > > patches touch zsmalloc locking (zspages migration/compaction).
> > >
> > > https://lore.kernel.org/lkml/20240219-b4-szmalloc-migrate-v1-0-34cd49c6545b@xxxxxxxxxxxxx/
> > 
> > These are not in 6.8.0-rc5 anyway, right?
> 
> I see them in next-20240223, which seems to be 6.8-rc6 (according to
                                                   ^ -rc5

But they look more or less correct to me, so I'm not blaming those
patches.  We should be protected by pool->look.  Bisection would help
us a lot, I think.




[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