From: Qinghua Jin <qhjin_dev@163.com>
To: unlisted-recipients:; (no To-header on input)
Cc: qhjin_dev@163.com, Colin Ian King <colin.king@canonical.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] vfs: fix bug when opening a file with O_DIRECT on a file system that does not support it will leave an empty file
Date: Tue, 4 Jan 2022 09:53:58 +0800 [thread overview]
Message-ID: <20220104015358.57443-1-qhjin_dev@163.com> (raw)
Colin Ian King reported the following
1. create a minix file system and mount it
2. open a file on the file system with O_RDWR | O_CREAT | O_TRUNC | O_DIRECT
3. open fails with -EINVAL but leaves an empty file behind. All other open() failures don't leave the
failed open files behind.
The reason is because when checking the O_DIRECT in do_dentry_open, the inode has created, and later err
processing can't remove the inode:
/* NB: we're sure to have correct a_ops only after f_op->open */
if (f->f_flags & O_DIRECT) {
if (!f->f_mapping->a_ops || !f->f_mapping->a_ops->direct_IO)
return -EINVAL;
}
The patch will check the O_DIRECT before creating the inode in lookup_open function.
Signed-off-by: Qinghua Jin <qhjin_dev@163.com>
Reported-by: Colin Ian King <colin.king@canonical.com>
---
fs/namei.c | 7 +++++++
fs/open.c | 6 ------
2 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 1f9d2187c765..24c6bcba702d 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -3277,6 +3277,13 @@ static struct dentry *lookup_open(struct nameidata *nd, struct file *file,
goto out_dput;
}
+ if (open_flag & O_DIRECT) {
+ if (!dir_inode->i_mapping || !dir_inode->i_mapping->a_ops ||
+ !dir_inode->i_mapping->a_ops->direct_IO) {
+ error = -EINVAL;
+ goto out_dput;
+ }
+ }
error = dir_inode->i_op->create(mnt_userns, dir_inode, dentry,
mode, open_flag & O_EXCL);
if (error)
diff --git a/fs/open.c b/fs/open.c
index f732fb94600c..2829c3613c0f 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -838,12 +838,6 @@ static int do_dentry_open(struct file *f,
file_ra_state_init(&f->f_ra, f->f_mapping->host->i_mapping);
- /* NB: we're sure to have correct a_ops only after f_op->open */
- if (f->f_flags & O_DIRECT) {
- if (!f->f_mapping->a_ops || !f->f_mapping->a_ops->direct_IO)
- return -EINVAL;
- }
-
/*
* XXX: Huge page cache doesn't support writing yet. Drop all page
* cache for this file before processing writes.
--
2.30.2
next reply other threads:[~2022-01-04 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 1:53 Qinghua Jin [this message]
2022-01-04 2:06 ` Al Viro
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=20220104015358.57443-1-qhjin_dev@163.com \
--to=qhjin_dev@163.com \
--cc=colin.king@canonical.com \
--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®