From: "Toralf Förster" <toralf.foerster@gmx.de>
To: bo.li.liu@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: fuzz testing a 32 bit x86 user mode linux guest brought a BUG in
Date: Mon, 25 Aug 2014 18:14:41 +0200 [thread overview]
Message-ID: <53FB60F1.6080902@gmx.de> (raw)
In-Reply-To: <20140825041213.GD22848@localhost.localdomain>
On 08/25/2014 06:12 AM, Liu Bo wrote:
> Could you please elaborate what options of trinity you're using?
>
> thanks,
> -liubo
$> nice trinity.sh -t "-C 2 -N 100000 -x mremap -x munmap -x madvise -q" -v /mnt/btrfs
So for UML I excluded in the past those 3 syscalls (nowadays no longer necessary), run 2 clients in parallel, the BTRFS fs was created in this manner :
dd if=/dev/zero of=/mnt/ramdisk/btrfs.fs bs=1M count=97 2>/dev/null; /sbin/mkfs.btrfs /mnt/ramdisk/btrfs.fs 1>/dev/null 2>&1; mount -o loop,compress=lzo /mnt/ramdisk/btrfs.fs /mnt/btrfs; chmod 777 /mnt/btrfs
--
Toralf
pgp key: 0076 E94E
next prev parent reply other threads:[~2014-08-25 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 21:56 fuzz testing a 32 bit x86 user mode linux guest brought a BUG in Toralf Förster
2014-08-25 4:12 ` Liu Bo
2014-08-25 16:14 ` Toralf Förster [this message]
2014-08-26 8:11 ` Liu Bo
2014-08-26 11:14 ` Liu Bo
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=53FB60F1.6080902@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@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).