mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <vdubeyko@redhat.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>,
	Viacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Hongling Zeng <zenghongling@kylinos.cn>
Subject: Re: [PATCH] nilfs2: Fix return in nilfs_mkdir
Date: Wed, 20 May 2026 11:22:45 -0700	[thread overview]
Message-ID: <5e93451665b895d2d9088dacda79683e691e5219.camel@redhat.com> (raw)
In-Reply-To: <20260520101600.19734-1-konishi.ryusuke@gmail.com>

On Wed, 2026-05-20 at 19:15 +0900, Ryusuke Konishi wrote:
> From: Hongling Zeng <zenghongling@kylinos.cn>
> 
> Return NULL instead of passing zero to ERR_PTR.
>   Fixes smatch warning:
>      - fs/nilfs2/namei.c:261 nilfs_mkdir() warn: passing zero to 'ERR_PTR'
> 
> Fixes: 88d5baf69082 ("Change inode_operations.mkdir to return struct dentry *")
> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
> Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
> ---
> Hi Viacheslav,
> 
> Please add this to the queue for the next cycle.
> 
> This is one of the fixes by Hongling Zeng, a patch that individually
> corrects a semantic issue (which is harmless in execution) related to
> the use of the ERR_PTR macro that arose from a recent VFS change.
> 
> Thanks,
> Ryusuke Konishi
> 
>  fs/nilfs2/namei.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/nilfs2/namei.c b/fs/nilfs2/namei.c
> index 40ac679ec56e..e2fe95de3d71 100644
> --- a/fs/nilfs2/namei.c
> +++ b/fs/nilfs2/namei.c
> @@ -258,7 +258,7 @@ static struct dentry *nilfs_mkdir(struct mnt_idmap *idmap, struct inode *dir,
>  	else
>  		nilfs_transaction_abort(dir->i_sb);
>  
> -	return ERR_PTR(err);
> +	return err ? ERR_PTR(err) : NULL;
>  
>  out_fail:
>  	drop_nlink(inode);

Applied.

Thanks,
Slava.


      reply	other threads:[~2026-05-20 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 10:15 Ryusuke Konishi
2026-05-20 18:22 ` Viacheslav Dubeyko [this message]

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=5e93451665b895d2d9088dacda79683e691e5219.camel@redhat.com \
    --to=vdubeyko@redhat.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --cc=zenghongling@kylinos.cn \
    /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

all inboxes | Powered by JetHome®