From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, Dave Jones <davej@redhat.com>
Subject: Re: found a scenario for BUG at fs/ext4/super.c:804!
Date: Sat, 01 Jun 2013 17:27:40 +0200 [thread overview]
Message-ID: <51AA12EC.6000001@gmx.de> (raw)
In-Reply-To: <51AA0CA1.6080600@redhat.com>
On 06/01/2013 05:00 PM, Eric Sandeen wrote:
> And therein lies the unknown magic.
>
> Again, trinity's job is to try to corrupt the kernel by fuzzing syscalls. We've had "xfs bug reports" after running trinity as well... and all indications are that xfs is the victim, not the root cause.
>
> It could be a filesystem bug, or just as easily some other bug in a syscall that allowed trinity to corrupt memory.
>
> I do not think these bug reports are actionable until you can figure out how to narrow down the trinity operations that cause the problem.
ok, I'm really trying to get a scenario without trinity.
I'm convinced that such a scenario does exist, just because kernel 3.9.4
does not run into those issue whereas 3.10 does.
--
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
next prev parent reply other threads:[~2013-06-01 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 17:58 found a scenario for BUG at fs/ext4/super.c:804! Toralf Förster
2013-05-30 18:06 ` Toralf Förster
2013-06-01 13:48 ` Toralf Förster
2013-06-01 15:00 ` Eric Sandeen
2013-06-01 15:27 ` Toralf Förster [this message]
2013-06-01 18:02 ` Toralf Förster
2013-07-06 9:38 ` Toralf Förster
2013-08-03 14:44 ` Toralf Förster
2013-08-03 15:36 ` Toralf Förster
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=51AA12EC.6000001@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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;
as well as URLs for NNTP newsgroup(s).