[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7cbf950-c732-4eb3-a91f-8f09249e4f72-pchelkin@ispras.ru>
Date: Thu, 14 Mar 2024 18:55:08 +0300
From: Fedor Pchelkin <pchelkin@...ras.ru>
To: Jens Axboe <axboe@...nel.dk>
Cc: Pavel Begunkov <asml.silence@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org, io-uring@...r.kernel.org,
linux-kernel@...r.kernel.org, Alexey Khoroshilov <khoroshilov@...ras.ru>,
lvc-project@...uxtesting.org, Nikita Zhandarovich <n.zhandarovich@...tech.ru>,
Roman Belyaev <belyaevrd@...dex.ru>
Subject: Re: [PATCH 5.10/5.15] io_uring: fix registered files leak
On 24/03/13 06:40PM, Jens Axboe wrote:
> Hi,
>
> OK, here they are. Two patches attached for every stable kernel, that
> gets rid of the remnants of the SCM related code:
>
> 5.4
> 5.10 and 5.15 (same patches)
> 6.1
> 6.6
> 6.7
>
> Would appreciate if Fedor and Pavel could give them a once over, but I
> think they are all fine. It's just deleting the code...
Thank you, Jens!
FWIW, I think it's all good and it eliminates the reported problem
obviously. Compiled and tested the repro with my kernel config.
Just a minor notice - stable rules declare two common ways for upstream
patch mentioning in backports [1]. And the first one starts from
lowercase. No big deal here definitely but maybe somebody has some
handling of these two variants - by regexps or similar, I actually don't
know. But I see in the git history that Greg also applies the variant
you've used.
[1]: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-3
--
Fedor
Powered by blists - more mailing lists