[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b574c8d6-c000-8673-74de-a7cc092057ad@linux.dev>
Date: Mon, 13 May 2024 11:25:38 +0800
From: Hao Ge <hao.ge@...ux.dev>
To: Markus Elfring <Markus.Elfring@....de>, Hao Ge <gehao@...inos.cn>,
linux-trace-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] eventfs: Directly return NULL to avoid null point
dereferenced
Hi Markus
Thanks for your review.
在 5/13/24 01:12, Markus Elfring 写道:
>> When the condition ei->is_free holds,we return NULL directly to
>> avoid update_events_attr to use NULL point about ei.
> * Please avoid typos in the summary phrase and the commit message.
>
> * Would you like to use an imperative wording for an improved change description?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc7#n94
>
>
> …
OK, I'll study it,
>> +++ b/fs/tracefs/event_inode.c
>> @@ -346,8 +346,7 @@ static struct eventfs_inode *eventfs_find_events(struct dentry *dentry)
>> * doesn't matter.
>> */
>> if (ei->is_freed) {
>> - ei = NULL;
>> - break;
>> + return NULL;
>> }
> …
>
> How do you think about to omit curly brackets here?
You are right, I will make changes to it in future versions
>
> Regards,
> Markus
Best Regards
Hao
Powered by blists - more mailing lists