From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: fuzzying a user mode linux image often core dumps with
Date: Sun, 21 Jul 2013 13:14:13 +0200 [thread overview]
Message-ID: <51EBC285.2030104@gmx.de> (raw)
In-Reply-To: <20130721010352.GB21484@thunk.org>
On 07/21/2013 03:03 AM, Theodore Ts'o wrote:
> On Sat, Jul 20, 2013 at 05:07:19PM +0200, Toralf Förster wrote:
>> I do run the fuzzer trinity within a 32 bit user mode linux.
>> With latest git tree I do often get a core dump like the one attached.
>>
>> Although it is the nature of trinity to corrupt the kernel /me wonders why it happens nearly alway
>> at the same place. That's why I decided to just report it here.
>
> Thanks, this is a known problem for which the fix is can be found here:
>
> http://patchwork.ozlabs.org/patch/260250/
>
Ah - so no bisecting necessary.
> I hope to get this fixed before -rc2 is released; the only question at
> the moment is whether the fix is going to go to Linus via the ext4
> tree or the VFS tree....
yep - Linus had it now in its tree-.
BTW that issue seems to be the reason for a lot of erratically crashes
of an UML while fuzzy tested.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-07-21 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 15:07 fuzzying a user mode linux image often core dumps with Toralf Förster
2013-07-21 1:03 ` Theodore Ts'o
2013-07-21 11:14 ` Toralf Förster [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=51EBC285.2030104@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).