From: Tejun Heo <tj@kernel.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: Waiman Long <longman@redhat.com>,
hannes@cmpxchg.org, mkoutny@suse.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] cgroup/cpuset: remove kernfs active break
Date: Wed, 8 Jan 2025 15:55:46 -1000 [thread overview]
Message-ID: <Z38sopf57DAusY9I@slm.duckdns.org> (raw)
In-Reply-To: <9250b4e8-8ef8-4a85-af24-14a34cc72e3b@huaweicloud.com>
On Thu, Jan 09, 2025 at 09:29:59AM +0800, Chen Ridong wrote:
> Hi, Tj and Longman, I am sorry, the fix tag is not exactly right. I just
> failed to reproduce this issue at the version 5.10, and I found this
> warning was added with the commit bdb2fd7fc56e ("kernfs: Skip
> kernfs_drain_open_files() more aggressively"), which is at version 6.1.
> I believe it should both fix bdb2fd7fc56e ("kernfs: Skip
> kernfs_drain_open_files() more aggressively") and 76bb5ab8f6e3 ("cpuset:
> break kernfs active protection in cpuset_write_resmask()"). Should I
> resend a new patch?
No worries. I updated the commit in place.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-01-09 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 8:19 [PATCH v2] cgroup/cpuset: remove kernfs active break Chen Ridong
2025-01-08 16:53 ` Tejun Heo
2025-01-08 19:27 ` Waiman Long
2025-01-08 19:35 ` Tejun Heo
2025-01-08 19:50 ` Waiman Long
2025-01-08 20:00 ` Tejun Heo
2025-01-08 20:04 ` Waiman Long
2025-01-08 19:20 ` Waiman Long
2025-01-08 19:23 ` Tejun Heo
2025-01-09 1:29 ` Chen Ridong
2025-01-09 1:55 ` Tejun Heo [this message]
2025-01-09 2:07 ` Chen Ridong
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=Z38sopf57DAusY9I@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox