[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f4e20f17-db56-4a3d-a673-b7349dde2495@web.de>
Date: Wed, 10 Sep 2025 16:01:55 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Kaushlendra Kumar <kaushlendra.kumar@...el.com>, rcu@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, Davidlohr Bueso <dave@...olabs.net>,
Frederic Weisbecker <frederic@...nel.org>,
Josh Triplett <josh@...htriplett.org>,
Neeraj Upadhyay <neeraj.upadhyay@...nel.org>,
"Paul E. McKenney" <paulmck@...nel.org>, Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH v3] rcu/rcutorture: Improve error handling in
rcu_torture_fwd_prog_init()
…> The improved approach:
> - Check rfp allocation immediately and return early on failure.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v6.17-rc5#n532
> - Separately handle fwd_prog_tasks allocation failure with proper
> cleanup of allocated resources.
> - Remove redundant kfree(fwd_prog_tasks) since it would be NULL on
> allocation failure.
Would it be cleaner to offer desirable changes by separate update steps?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17-rc5#n81
How do you think about to increase the application of scope-based resource management?
Regards,
Markus
Powered by blists - more mailing lists