From: Alex Elder <aelder@sgi.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: <xfs@oss.sgi.com>, <linux-ext4@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 2/2] xfstest: fsstress add EXT2_IOC_{SET,GET}FLAGS operations
Date: Wed, 5 Oct 2011 08:20:40 -0500 [thread overview]
Message-ID: <1317820840.2226.12.camel@doink> (raw)
In-Reply-To: <1316357699-22692-2-git-send-email-dmonakhov@openvz.org>
On Sun, 2011-09-18 at 18:54 +0400, Dmitry Monakhov wrote:
> Add two new operations:
> - getattr: ioctl(fd, EXT2_IOC_GETFLAGS, &fl)
> - setattr: ioctl(fd, EXT2_IOC_SETFLAGS, &random_flags)
> By default IOC_SET_SETFLAGS has zero probability because
> it may produce inodes with APPEND or IMMUTABLE flags which
> are not deletable by default. Let's assumes that one who
> enable it knows how to delete such inodes.
> For example like follows:
> find $TEST_PATH -exec chattr -i -a {} \;
> rm -rf $TEST_PATH
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
I have a question below. I think this is probably
a good addition, though it should be made so it
works for more than EXTx.
If I understand the way it would be used, this will
simply be another operation that gets randomly performed
by fsstress while it operates, right?
I have not done any testing with this yet.
Reviewed-by: Alex Elder <aelder@sgi.com>
. . .
> @@ -1729,6 +1738,58 @@ setxattr_f(int opno, long r)
> }
>
> void
> +getattr_f(int opno, long r)
> +{
> +#ifdef HAVE_EXT2_INCLUDE
> + int fd;
> + int e;
> + pathname_t f;
> + uint fl;
> + int v;
> +
> + init_pathname(&f);
> + if (!get_fname(FT_ANYm, r, &f, NULL, NULL, &v))
> + append_pathname(&f, ".");
I don't understand the purpose of appending a "." to the
end of the path. Do you intend to just use "." if
no other file matches? (That may not be a good thing to
do--it might not be testing the intended target.)
Or are you intending to append "/." so for a directory
its "." link gets used in the open? If so that's not
what this does (it simply makes "a/b/x" become "a/b/x.").
Same comments apply to setattr_f().
> + fd = open_path(&f, O_RDWR);
> + e = fd < 0 ? errno : 0;
> + check_cwd();
> +
> + e = ioctl(fd, EXT2_IOC_GETFLAGS, &fl);
> + if (v)
> + printf("%d/%d: getattr %s %u %d\n", procid, opno, f.path, fl, e);
> + free_pathname(&f);
> + close(fd);
> +#endif
> +}
> +
> +void
> +setattr_f(int opno, long r)
> +{
next prev parent reply other threads:[~2011-10-05 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 14:54 [PATCH 1/2] xfstest: fsstress should kill children tasks before exit Dmitry Monakhov
2011-09-18 14:54 ` [PATCH 2/2] xfstest: fsstress add EXT2_IOC_{SET,GET}FLAGS operations Dmitry Monakhov
2011-09-18 20:03 ` Christoph Hellwig
2011-10-05 13:20 ` Alex Elder [this message]
2011-10-06 9:21 ` Dmitry Monakhov
2011-10-19 9:28 ` [PATCH 2/2] xfstest: fsstress add EXT2_IOC_{SET, GET}FLAGS operations Christoph Hellwig
2011-10-19 10:48 ` Dmitry Monakhov
2011-10-06 19:52 ` [PATCH 2/2] xfstest: fsstress add EXT2_IOC_{SET,GET}FLAGS operations Christoph Hellwig
2011-10-05 13:20 ` [PATCH 1/2] xfstest: fsstress should kill children tasks before exit Alex Elder
2011-10-05 13:41 ` Dmitry Monakhov
2011-10-06 19:51 ` Christoph Hellwig
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=1317820840.2226.12.camel@doink \
--to=aelder@sgi.com \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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).