From: Rich Johnston <rjohnston@sgi.com>
To: Eryu Guan <eguan@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/4] xfstests: random regression tests
Date: Fri, 5 Apr 2013 08:41:50 -0500 [thread overview]
Message-ID: <515ED49E.6020406@sgi.com> (raw)
In-Reply-To: <1364813864-10820-1-git-send-email-eguan@redhat.com>
Thanks for submitting this patchset, it has been committed.
--Rich
commit 797c82f0e22528df369cf198c2a9d6109e085838
Author: Eryu Guan <eguan@redhat.com>
Date: Mon Apr 1 10:57:44 2013 +0000
xfstests generic 309: test dir mtime and ctime are updated on rename
Test directory mtime and ctime are updated when moving a file onto an
existing file in the directory
Regression test for commit:
0b23076 ext3: fix update of mtime and ctime on rename
Signed-off-by: Eryu Guan <eguan@redhat.com>
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
[rjohnston@sgi.com renumbered test to next in group sequence]
Signed-off-by: Rich Johnston <rjohnston@sgi.com>
commit f7922730727844c6dee837bd1a64221342fef1d1
Author: Eryu Guan <eguan@redhat.com>
Date: Mon Apr 1 10:57:43 2013 +0000
xfstests ext4 305: test read /proc/fs/ext4/<dev>/mb_groups while
the fs is being unmounted
Regression test for commit:
9559996 ext4: remove mb_groups before tearing down the buddy_cache
Signed-off-by: Eryu Guan <eguan@redhat.com>
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
[rjohnston@sgi.com renumbered test to next in group sequence]
Signed-off-by: Rich Johnston <rjohnston@sgi.com>
commit 94e1e7e53a89d9a3387bee7dea60091afaf79704
Author: Eryu Guan <eguan@redhat.com>
Date: Mon Apr 1 10:57:42 2013 +0000
xfstests generic 308: test write to the last block of max file size
on ext4
On unpatched ext4 if an extent exists which includes the block right
before the maximum file offset, and the block for the maximum file
offset is written, the kernel panics.
On patched ext4, the write would get EFBIG since we lower s_maxbytes
by one fs block.
Regression test for commit:
f17722f ext4: Fix max file size and logical block counting of
extent format file
Though it's an ext4 specific issue, it's no harm to run on all file
systems, so put it in generic.
Signed-off-by: Eryu Guan <eguan@redhat.com>
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
[rjohnston@sgi.com renumbered test to next in group sequence]
Signed-off-by: Rich Johnston <rjohnston@sgi.com>
commit 6422b818388c652183b6b517be1feac554f5f004
Author: Eryu Guan <eguan@redhat.com>
Date: Mon Apr 1 10:57:41 2013 +0000
xfstests generic 307: check ctime updates for setfacl
Check if ctime is updated and written to disk after setfacl
Regression test for the following extN commits
c6ac12a ext4: update ctime when changing the file's permission by
setfacl
30e2bab ext3: update ctime when changing the file's permission by
setfacl
523825b ext2: update ctime when changing the file's permission by
setfacl
Signed-off-by: Eryu Guan <eguan@redhat.com>
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
[rjohnston@sgi.com renumbered test to next in group sequence]
Signed-off-by: Rich Johnston <rjohnston@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-04-05 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 10:57 [PATCH 0/4] xfstests: random regression tests Eryu Guan
2013-04-01 10:57 ` [PATCH 2/4] xfstests generic 309: test write to the last block of max file size on ext4 Eryu Guan
2013-04-05 13:38 ` Rich Johnston
2013-04-01 10:57 ` [PATCH 3/4] xfstests ext4 310: test read /proc/fs/ext4/<dev>/mb_groups while the fs is being unmounted Eryu Guan
2013-04-05 13:38 ` Rich Johnston
2013-04-01 10:57 ` [PATCH 4/4] xfstests generic 311: test dir mtime and ctime are updated on rename Eryu Guan
2013-04-05 13:38 ` Rich Johnston
2013-04-05 13:41 ` Rich Johnston [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=515ED49E.6020406@sgi.com \
--to=rjohnston@sgi.com \
--cc=eguan@redhat.com \
--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