From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-nfs@vger.kernel.org
Cc: Olga Kornievskaia <kolga@netapp.com>, linux-fsdevel@vger.kernel.org
Subject: [RFC] problems with alloc_file_pseudo() use in __nfs42_ssc_open()
Date: Wed, 17 Aug 2022 22:55:14 +0100 [thread overview]
Message-ID: <Yv1jwsHVWI+lguAT@ZenIV> (raw)
My apologies for having missed that back when the SSC
patchset had been done (and missing the problems after it got
merged, actually).
1) if this
r_ino = nfs_fhget(ss_mnt->mnt_sb, src_fh, fattr);
in __nfs42_ssc_open() yields a directory inode, we are screwed
as soon as it's passed to alloc_file_pseudo() - a *lot* of places
in dcache handling would break if we do that. It's not too
nice for a regular file from non-cooperating filesystem, but for
directory ones it's deadly.
2) if alloc_file_pseudo() fails there, we get an inode leak. It
needs an iput() for that case. As in
if (IS_ERR(filep)) {
res = ERR_CAST(filep);
iput(r_ino);
goto out_free_name;
}
But I'd like to point out that alloc_file_pseudo() is not inteded for
use on normal filesystem's inodes - the use here *mostly* works
(directories aside), but... Use it on filesystem with non-trivial
default dentry_operations and things will get interesting, etc.
next reply other threads:[~2022-08-17 21:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 21:55 Al Viro [this message]
2022-08-17 22:32 ` [RFC] problems with alloc_file_pseudo() use in __nfs42_ssc_open() Olga Kornievskaia
2022-08-18 0:01 ` Al Viro
2022-08-18 0:12 ` Olga Kornievskaia
2022-08-18 0:20 ` Al Viro
2022-08-18 5:19 ` Amir Goldstein
2022-08-18 5:52 ` Al Viro
2022-08-18 13:13 ` Olga Kornievskaia
2022-08-18 14:38 ` Trond Myklebust
2022-08-19 2:51 ` dai.ngo
2022-08-19 14:22 ` Olga Kornievskaia
2022-08-19 15:42 ` dai.ngo
2022-08-19 17:37 ` Olga Kornievskaia
2022-08-19 18:18 ` dai.ngo
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=Yv1jwsHVWI+lguAT@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=kolga@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.