From: hch <hch@lst.de>
To: Waiman Long <llong@redhat.com>
Cc: hch <hch@lst.de>, Kamaljit Singh <Kamaljit.Singh1@wdc.com>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: cgroup null pointer dereference
Date: Fri, 25 Apr 2025 17:26:04 +0200 [thread overview]
Message-ID: <20250425152604.GA15999@lst.de> (raw)
In-Reply-To: <8a85a074-d4fe-404e-9438-131963a51051@redhat.com>
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.
next prev parent reply other threads:[~2025-04-25 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 17:30 cgroup null pointer dereference Kamaljit Singh
2025-04-23 21:26 ` Waiman Long
2025-04-25 0:53 ` Kamaljit Singh
2025-04-25 1:33 ` Waiman Long
2025-04-25 1:43 ` Waiman Long
2025-04-25 1:49 ` Waiman Long
2025-04-25 2:22 ` Kamaljit Singh
2025-04-25 14:54 ` hch
2025-04-25 15:04 ` Waiman Long
2025-04-25 15:11 ` hch
2025-04-25 15:22 ` Waiman Long
2025-04-25 15:26 ` hch [this message]
2025-04-25 17:20 ` Kamaljit Singh
2025-04-25 17:20 ` Kamaljit Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250425152604.GA15999@lst.de \
--to=hch@lst.de \
--cc=Kamaljit.Singh1@wdc.com \
--cc=cgroups@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=llong@redhat.com \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.