Re: [PATCH v2] kasan, mempool: don't store free stacktrace in io_alloc_cache objects.

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

Subject: Re: [PATCH v2] kasan, mempool: don't store free stacktrace in io_alloc_cache objects.
From: Jens Axboe <axboe@xxxxxxxxx>
Date: Thu, 30 Jan 2025 09:02:15 -0700
Cc: kasan-dev@xxxxxxxxxxxxxxxx, io-uring@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, netdev@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, juntong.deng@xxxxxxxxxxx, lizetao1@xxxxxxxxxx, stable@xxxxxxxxxxxxxxx, Alexander Potapenko <glider@xxxxxxxxxx>, Andrey Konovalov <andreyknvl@xxxxxxxxx>, Dmitry Vyukov <dvyukov@xxxxxxxxxx>, Vincenzo Frascino <vincenzo.frascino@xxxxxxx>, Pavel Begunkov <asml.silence@xxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, Eric Dumazet <edumazet@xxxxxxxxxx>, Jakub Kicinski <kuba@xxxxxxxxxx>, Paolo Abeni <pabeni@xxxxxxxxxx>, Simon Horman <horms@xxxxxxxxxx>
In-reply-to: <20250127150357.13565-1-ryabinin.a.a@gmail.com>
User-agent: Mozilla Thunderbird

I don't think we need this with the recent cleanup of the io_uring
struct caching. That should go into 6.14-rc1, it's queued up. So I think
let's defer on this one for now? It'll conflict with those changes too.

-- 
Jens Axboe

References:
- [PATCH] kasan, mempool: don't store free stacktrace in io_alloc_cache objects.
  - From: Andrey Ryabinin
- [PATCH v2] kasan, mempool: don't store free stacktrace in io_alloc_cache objects.
  - From: Andrey Ryabinin

Prev by Date: Re: [PATCH 6.1.y v2] gpio: xilinx: Convert gpio_lock to raw spinlock
Next by Date: Re: [PATCH 0/2] A couple of build fixes for x86 when using GCC 15
Previous by thread: Re: [PATCH v2] kasan, mempool: don't store free stacktrace in io_alloc_cache objects.
Next by thread: [PATCH v3 6/6] ima: Reset IMA_NONACTION_RULE_FLAGS after post_setattr
Index(es):
- Date
- Thread

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