From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/2] fs: unreference path on file close
Date: Tue, 24 Jun 2025 13:36:56 +0200 [thread overview]
Message-ID: <d705d530-413d-4dd9-b07c-d16d7f4fd4e6@pengutronix.de> (raw)
In-Reply-To: <20250611115635.3341350-1-s.hauer@pengutronix.de>
Hi,
On 6/11/25 13:56, Sascha Hauer wrote:
> Since commit 83ffe89840e8 ("fs: use filename_create/filename_lookup
> instead of open-coding") we no longer open-code the file lookup during
> openat(). Unlike the open-coded variant filename_lookup() keeps a
> reference to the file which is now leaked and the filesystem cannot be
> unmounted anymore:
>
> umount: Device or resource busy
>
> Since commit a1da0079d162 ("fs: implement opendir in terms of fdopendir")
> this also happens when just a directory is opened.
>
> The original code was not quite correct: After calling terminate_walk()
> we no longer held a reference to the path for an opened file. Transfer
> the path to the already existing f_path in struct file and unreference
> it a close() time.
Unfortunately, this introduced a regression to v2025.06.0:
Before:
barebox@TI AM335x BeagleBone black:/ rm /mnt/mmc0.0/barebox.env
barebox@TI AM335x BeagleBone black:/ saveenv
saving environment to /mnt/mmc0.0/barebox.env
barebox@TI AM335x BeagleBone black:/ saveenv
saving environment to /mnt/mmc0.0/barebox.env
After:
barebox@TI AM335x BeagleBone black:/ rm /mnt/mmc0.0/barebox.env
barebox@TI AM335x BeagleBone black:/ saveenv
saving environment to /mnt/mmc0.0/barebox.env
could not open /mnt/mmc0.0/barebox.env: Invalid argument
saveenv: Invalid argument
barebox@TI AM335x BeagleBone black:/ saveenv
saving environment to /mnt/mmc0.0/barebox.env
The -EINVAL comes from fat_open being called with / as filename.
I am not yet sure what the proper fix is. At least we have a test
now to avoid the old regression from reocurring...
Cheers,
Ahmad
>
> Fixes: 83ffe89840e8 ("fs: use filename_create/filename_lookup instead of open-coding")
> Fixes: a1da0079d162 ("fs: implement opendir in terms of fdopendir")
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> fs/fs.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/fs.c b/fs/fs.c
> index d401268c1e..18343552a7 100644
> --- a/fs/fs.c
> +++ b/fs/fs.c
> @@ -330,7 +330,7 @@ static void put_file(struct file *f)
> f->path = NULL;
> f->fsdev = NULL;
> iput(f->f_inode);
> - dput(f->f_dentry);
> + path_put(&f->f_path);
> }
>
> static struct file *fd_to_file(int fd, bool o_path_ok)
> @@ -2550,7 +2550,7 @@ int openat(int dirfd, const char *pathname, int flags)
> int error = 0;
> struct inode *inode = NULL;
> struct dentry *dentry = NULL;
> - struct path path;
> + struct path path = {};
>
> if (flags & O_TMPFILE) {
> error = filename_lookup(dirfd, getname(pathname), LOOKUP_DIRECTORY, &path);
> @@ -2628,11 +2628,12 @@ int openat(int dirfd, const char *pathname, int flags)
> f = get_file(fsdev);
> if (!f) {
> error = -EMFILE;
> + path_put(&path);
> goto out1;
> }
>
> f->path = dpath(dentry, d_root);
> - f->f_dentry = dentry;
> + f->f_path = path;
> f->f_inode = iget(inode);
> f->f_flags = flags;
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-06-24 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 11:56 Sascha Hauer
2025-06-11 11:56 ` [PATCH 2/2] fs: unreference path in canonicalize_path() Sascha Hauer
2025-06-12 7:39 ` [PATCH 1/2] fs: unreference path on file close Sascha Hauer
2025-06-24 11:36 ` Ahmad Fatoum [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=d705d530-413d-4dd9-b07c-d16d7f4fd4e6@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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