From: Eryu Guan <eguan@redhat.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v8 1/2] fsstress: add mwrite/mread into test operation list
Date: Sun, 26 Mar 2017 02:14:40 +0800 [thread overview]
Message-ID: <20170325181440.GM14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1490256627-32034-1-git-send-email-zlang@redhat.com>
On Thu, Mar 23, 2017 at 04:10:26PM +0800, Zorro Lang wrote:
> mmap as a popular and basic operation, most of softwares use it to
> access files. More and more customers report bugs related with
> mmap/munmap and other stress conditions.
>
> So add mmap read/write test into fsstress to increase mmap related
> stress to reproduce or find more bugs easily.
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
generic/270 failed in my release testing because fsstress processes
exited early than expected and killall complained no process to kill.
+/tmp/4881.fsstress.bin: no process found
This is because mwrite would trigger SIGBUS if it's writing to a mmap'ed
hole and there's no space left on device, so fsstress processes are
killed by SIGBUS.
Perhaps SIGBUS should be caught and handled so that fsstress won't be
killed. I'll drop this patchset for now.
Thanks,
Eryu
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=-yMrTV4jriXR7ieyzzjV-QgHBD0UDw8ixoR77aMeAHE&m=2t9HwWh4wP8emNipoxUCyrfBolWLtO4Wo7L03917srA&s=lkhxQRQxn4bXpG6hIo_G2QfP29bYUIN8QQ9D32aQIEM&e=
prev parent reply other threads:[~2017-03-25 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 8:10 [PATCH v8 1/2] fsstress: add mwrite/mread into test operation list Zorro Lang
2017-03-23 8:10 ` [PATCH v8 2/2] xfs/068: update golden output due to new operations in fsstress Zorro Lang
2017-03-25 18:14 ` Eryu Guan [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=20170325181440.GM14226@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=zlang@redhat.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