From: Jan Kara <jack@suse.cz>
To: Eryu Guan <guaneryu@gmail.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] ext3: Avoid creating new file in append-only dir when open(2) return error
Date: Wed, 2 Nov 2011 00:10:34 +0100 [thread overview]
Message-ID: <20111101231034.GI18701@quack.suse.cz> (raw)
In-Reply-To: <1319824987-5621-1-git-send-email-guaneryu@gmail.com>
On Sat 29-10-11 02:03:07, Eryu Guan wrote:
> Newly created file on ext3 inherits inode flags from parent directory,
> so new inode created in append-only directory has S_APPEND flag set,
> may_open() called by do_last() checks that flag then returns -EPERM,
> but at that time the new inode is already created.
>
> This can be reproduced by:
> # mkdir -p /mnt/ext3/append-only
> # chattr +a /mnt/ext3/append-only
> # ./opentest /mnt/ext3/append-only/newtestfile
> # ls -l /mnt/ext3/append-only/newtestfile
>
> opentest will return 'Operation not permitted', but the ls shows that
> newtestfile is already created.
>
> # cat opentest.c
> #include <stdio.h>
> #include <sys/types.h>
> #include <fcntl.h>
> #include <sys/stat.h>
>
> int main(int argc, char *argv[])
> {
> int fd;
> fd = open(argv[1], O_RDWR|O_CREAT, 0666);
> if (fd == -1)
> perror("open failed");
> return 0;
> }
>
> To avoid this, check EXT3_APPEND_FL flag first in ext3_create before
> really allocating new inode.
Yes, it is nicer to not create any file when open(2) fails in the end.
BTW, how have you spotted this? I've taken your ext2 and ext3 patches into
my tree.
Honza
>
> Cc: Jan Kara <jack@suse.cz>
> Signed-off-by: Eryu Guan <guaneryu@gmail.com>
> ---
> fs/ext3/namei.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ext3/namei.c b/fs/ext3/namei.c
> index 0629e09..323cf2f 100644
> --- a/fs/ext3/namei.c
> +++ b/fs/ext3/namei.c
> @@ -36,6 +36,7 @@
> #include <linux/quotaops.h>
> #include <linux/buffer_head.h>
> #include <linux/bio.h>
> +#include <linux/namei.h>
> #include <trace/events/ext3.h>
>
> #include "namei.h"
> @@ -1704,6 +1705,15 @@ static int ext3_create (struct inode * dir, struct dentry * dentry, int mode,
> handle_t *handle;
> struct inode * inode;
> int err, retries = 0;
> + int open_flag = nd->intent.open.file->f_flags;
> +
> + if ((EXT3_I(dir)->i_flags & EXT3_FL_INHERITED) & EXT3_APPEND_FL) {
> + if ((open_flag & O_ACCMODE) != O_RDONLY &&
> + !(open_flag & O_APPEND))
> + return -EPERM;
> + if (open_flag & O_TRUNC)
> + return -EPERM;
> + }
>
> dquot_initialize(dir);
>
> --
> 1.7.7.1
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2011-11-01 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 18:03 [PATCH] ext3: Avoid creating new file in append-only dir when open(2) return error Eryu Guan
2011-11-01 23:10 ` Jan Kara [this message]
2011-11-01 23:27 ` Ted Ts'o
2011-11-02 14:23 ` Jan Kara
2011-11-02 2:05 ` Eryu Guan
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=20111101231034.GI18701@quack.suse.cz \
--to=jack@suse.cz \
--cc=guaneryu@gmail.com \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).