From: Theodore Ts'o <tytso@mit.edu>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-ext4@vger.kernel.org,
UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: fuzz testing an ext4fs file system under a 32 bit Linux user mode linux guest let task jbd2/ubda hang
Date: Sat, 9 Aug 2014 16:00:18 -0400 [thread overview]
Message-ID: <20140809200018.GG15431@thunk.org> (raw)
In-Reply-To: <53E66C57.8010303@gmx.de>
On Sat, Aug 09, 2014 at 08:45:43PM +0200, Toralf Förster wrote:
>
> BTW may I just ask, if the following (same 32 bit system, host and
> UML guest are both at v3.16, 4 trinity childs hammering victims
> files in a ramdisk within the uML guest) matches the above too ? Or
> does the BUG output here more helpful data ? :
Unfortunately, there's nothing useful here. There is more than one
BUG_ON() in this mpage_release_unused_pages function, and what's more,
we have no idea which syscall or combination of syscalls might have
left a page in a particular state.
- Ted
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-ext4@vger.kernel.org,
UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] fuzz testing an ext4fs file system under a 32 bit Linux user mode linux guest let task jbd2/ubda hang
Date: Sat, 9 Aug 2014 16:00:18 -0400 [thread overview]
Message-ID: <20140809200018.GG15431@thunk.org> (raw)
In-Reply-To: <53E66C57.8010303@gmx.de>
On Sat, Aug 09, 2014 at 08:45:43PM +0200, Toralf Förster wrote:
>
> BTW may I just ask, if the following (same 32 bit system, host and
> UML guest are both at v3.16, 4 trinity childs hammering victims
> files in a ramdisk within the uML guest) matches the above too ? Or
> does the BUG output here more helpful data ? :
Unfortunately, there's nothing useful here. There is more than one
BUG_ON() in this mpage_release_unused_pages function, and what's more,
we have no idea which syscall or combination of syscalls might have
left a page in a particular state.
- Ted
------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2014-08-09 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 13:52 fuzz testing an ext4fs file system under a 32 bit Linux user mode linux guest let task jbd2/ubda hang Toralf Förster
2014-08-03 13:52 ` [uml-devel] " Toralf Förster
2014-08-03 18:42 ` Theodore Ts'o
2014-08-03 18:42 ` [uml-devel] " Theodore Ts'o
2014-08-09 18:45 ` Toralf Förster
2014-08-09 18:45 ` [uml-devel] " Toralf Förster
2014-08-09 20:00 ` Theodore Ts'o [this message]
2014-08-09 20:00 ` Theodore Ts'o
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=20140809200018.GG15431@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--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 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.