[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<BY5PR04MB68493CECDBCFCB26237CD5AABC842@BY5PR04MB6849.namprd04.prod.outlook.com>
Date: Fri, 25 Apr 2025 17:20:19 +0000
From: Kamaljit Singh <Kamaljit.Singh1@....com>
To: hch <hch@....de>, Waiman Long <llong@...hat.com>
CC: hch <hch@....de>, "cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"kbusch@...nel.org" <kbusch@...nel.org>, "sagi@...mberg.me"
<sagi@...mberg.me>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: cgroup null pointer dereference
Christoph,
>On Fri, Apr 25, 2025 at 11:22:50AM -0400, Waiman Long wrote:
>> The nvme-6.15-2025-04-10 branch used by Kmaljit includes some v6.15
>> commits like the cgroup commit 093c8812de2d3 ("cgroup: rstat:
>> Cleanup flushing functions and locking") but not its fix commit
>> 7d6c63c31914 ("cgroup: rstat: call cgroup_rstat_updated_list with
>> cgroup_rstat_lock"). That can cause system crash in some cases. That
>> problem will be resolved if nvme is rebased on top of v6.15-rc1 or
>> later as the fix commit will be included.
>
>The nvme branches are always rebased on top of the current relevant block
>branches, i.e. block-6.15 in thise case. Everything else would create
>merge issues.
Please ignore my request.
I'll pull in from the mainline. Thanks Damien!
Powered by blists - more mailing lists