From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@redhat.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@infradead.org>
Cc: Brian Foster <bfoster@redhat.com>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/3] xfs/348: test handling of malformed inode mode
Date: Sun, 25 Dec 2016 20:09:33 +0200 [thread overview]
Message-ID: <1482689376-23553-1-git-send-email-amir73il@gmail.com> (raw)
Eryu,
I beefed up the initial test sent earlier today with more checks
on mounted fs.
The original patch testing only xfs_repair remains patch 1 in this series.
Patch 2 adds fstat tests on mounted fs, which are safe on my test system.
Patch 3 is explosive. It exposes an XFS assert, but I left a "safety pin"
that needs to be commented out to reproduce the assert.
I will soon post my kernel configs and dmesg logs.
Amir.
v2:
- test fstat with malformed inode mode
- test readlink/readdir with malformed inode mode
v1:
- test xfs_repair with malformed inode mode
Amir Goldstein (3):
xfs/348: test handling of invalid inode modes
xfs/348: test fstat with malformed inode mode
xfs/348: test readlink/readdir with malformed inode mode
tests/xfs/348 | 154 +++++++++++++++++++++++++++
tests/xfs/348.out | 312 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/group | 1 +
3 files changed, 467 insertions(+)
create mode 100755 tests/xfs/348
create mode 100644 tests/xfs/348.out
--
2.7.4
next reply other threads:[~2016-12-25 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 18:09 Amir Goldstein [this message]
2016-12-25 18:09 ` [PATCH v2 1/3] xfs/348: test handling of invalid inode modes Amir Goldstein
2017-01-03 20:36 ` Darrick J. Wong
2017-01-04 10:36 ` Amir Goldstein
2017-01-04 20:33 ` Darrick J. Wong
2016-12-25 18:09 ` [PATCH v2 2/3] xfs/348: test fstat with malformed inode mode Amir Goldstein
2016-12-25 18:09 ` [PATCH v2 3/3] xfs/348: test readlink/readdir " Amir Goldstein
2017-01-03 5:52 ` [PATCH v2 0/3] xfs/348: test handling of " Eryu Guan
2017-01-11 6:45 ` Amir Goldstein
2017-01-11 9:08 ` 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=1482689376-23553-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.