From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Jan Kara <jack@suse.cz>, Dan Carpenter <error27@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] vfs: clean up indenting in lookup_open()
Date: Tue, 15 Sep 2026 23:56:16 +0200 (CEST) [thread overview]
Message-ID: <1913061521.1120051.1789509376030@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <hftpz62zoc7rjn3xdcaqgnujjnicpgv6betqbqfyvp45tynmep@l7m75b46jxpz>
This is about linux-next, right?
This should not have been pulled into next yet. I rebased this series after
Neil's vfs_lookup_open() landed in 7.3. There were some rebasing conflicts that
I fixed, but I left something out, which I fixed later but forgot to format-patch
again when sending out (including this whitespace). Christian pointed this
out to me, and I have fixed these things in v6 of O_CREAT|O_DIRECTORY.[1]
Please, pull that into vfs tree and then next. Some of the patches also need an
explicit review still, although Neil looked through most of it. Maybe you want
to take a look as well, Jan? :)
[1]: https://lore.kernel.org/linux-fsdevel/20260913185016.523376-1-jkoolstra@xs4all.nl/
> Op 15-09-2026 22:40 CEST schreef Jan Kara <jack@suse.cz>:
>
>
> On Tue 15-09-26 19:37:53, Dan Carpenter wrote:
> > These lines are indented too far. Delete a tab.
> >
> > Signed-off-by: Dan Carpenter <error27@gmail.com>
>
> Looks good. Feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
>
> Honza
>
> > ---
> > fs/namei.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/namei.c b/fs/namei.c
> > index 1dd4ec7d0e62..48b28ed44a9e 100644
> > --- a/fs/namei.c
> > +++ b/fs/namei.c
> > @@ -4636,9 +4636,9 @@ static struct dentry *lookup_open(struct nameidata *nd, struct file *file,
> > if (create_dir) {
> > struct dentry *res = vfs_mkdir_no_perm(idmap, dir_inode, dentry,
> > mode, &delegated_inode);
> > - error = PTR_ERR_OR_ZERO(res);
> > - if (!error)
> > - dentry = res;
> > + error = PTR_ERR_OR_ZERO(res);
> > + if (!error)
> > + dentry = res;
> > } else {
> > error = vfs_create_no_perm(idmap, dentry, mode, &delegated_inode);
> > }
> > --
> > 2.53.0
> >
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
prev parent reply other threads:[~2026-09-15 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 16:37 Dan Carpenter
2026-09-15 20:40 ` Jan Kara
2026-09-15 21:56 ` Jori Koolstra [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=1913061521.1120051.1789509376030@kpc.webmail.kpnmail.nl \
--to=jkoolstra@xs4all.nl \
--cc=brauner@kernel.org \
--cc=error27@gmail.com \
--cc=jack@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®