All of lore.kernel.org
 help / color / mirror / Atom feed
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 20:02:36 +0200	[thread overview]
Message-ID: <51AA373C.4060801@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

Just one question :
Is trinity able to corrupt the host kernel while running within a user
mode linux guest ?

Because it is the host kernel which fails after being attacked with a
lot of NFS calls.

-- 
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

  parent reply	other threads:[~2013-06-01 18:02 UTC|newest]

Thread overview: 11+ 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
2013-06-01 18:02   ` Toralf Förster [this message]
2013-07-06  9:38   ` 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
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=51AA373C.4060801@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 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.