[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YF3RLAYbewYS7vqc@kroah.com>
Date: Fri, 26 Mar 2021 13:18:52 +0100
From: Greg KH <greg@...ah.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: mingo@...nel.org, mgorman@...e.de, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, bristot@...hat.com,
joshdon@...gle.com, valentin.schneider@....com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 6/9] debugfs: Implement debugfs_create_str()
On Fri, Mar 26, 2021 at 12:38:39PM +0100, Peter Zijlstra wrote:
> On Fri, Mar 26, 2021 at 12:30:24PM +0100, Greg KH wrote:
> > Great, change that and limit the size of the string that can be written
> > and it looks good to me, thanks for adding this.
>
> Here goes..
Great, except one tiny thing:
> + * This function will return a pointer to a dentry if it succeeds. This
> + * pointer must be passed to the debugfs_remove() function when the file is
> + * to be removed (no automatic cleanup happens if your module is unloaded,
> + * you are responsible here.) If an error occurs, ERR_PTR(-ERROR) will be
> + * returned.
> + *
> + * NOTE: when writing is enabled it will replace the string, string lifetime is
> + * assumed to be RCU managed.
> + *
> + * If debugfs is not enabled in the kernel, the value ERR_PTR(-ENODEV) will
> + * be returned.
Nothing is returned anymore so the top and bottom paragraphs here no
longer apply.
Fix that up and feel free to add:
Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
thanks,
greg k-h
Powered by blists - more mailing lists