public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How do I get the ext3 driver to shut up?
Date: Tue, 14 Mar 2006 10:20:27 -0500	[thread overview]
Message-ID: <200603141020.27963.rob@landley.net> (raw)
In-Reply-To: <20060313193027.b0eae48e.rdunlap@xenotime.net>

[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]

On Monday 13 March 2006 10:30 pm, Randy.Dunlap wrote:
> On Mon, 13 Mar 2006 22:18:39 -0500 Rob Landley wrote:
> > I'm making a test suite for busybox mount, which does filesystem
> > autodetection the easy way (try all the ones in /etc/filesystems and
> > /proc/filesystems until one of them succeeds).  My test code is creating
> > and mounting vfat and ext2 filesystems.
> >
> > Guess which device driver feels a bit chatty?
> >
> > PASS: mount no proc [GNUFAIL]
> > PASS: mount /proc
> > PASS: mount list1
> > VFS: Can't find ext3 filesystem on dev loop0.
> > PASS: mount vfat image (autodetect type)
> > ext3: No journal on filesystem on loop1
> > PASS: mount ext2 image (autodetect type)
> > PASS: mount remount ext2 image noatime
> > PASS: mount remount ext2 image ro remembers noatime
> > ext3: No journal on filesystem on loop0
> > PASS: umount freed loop device
> > PASS: mount remount nonexistent directory
> > PASS: mount -a no fstab
>
> Hrm, yes, 2 of those lines do come from ext3.

Three, actually.

> Where do the rest of them come from?

My half-finished regression test suite for busybox mount.  I just rewrote the 
busybox "mount" command to fix a half-dozen bugs (the hardest of which was 
making it properly reentrant so "mount -a" behaves properly).  And I 
basically had to derive a spec for mount from first principles (which I've 
halfway written up, should probably finish and post somewhere), and now I'm 
writing The Regression Test Of Doom.

It runs under User Mode Linux, so it has a nice little clean root environment 
to work in and there's no worry about cleanup for when I typo something in 
the script and it crashes halfway through, because when the UML environment 
exits it takes its current mounts with it.  Eventually I'll probably get it 
to run under a normal root environment...

Let's see...  Tarball attached, and I've been running it with:
~/linux-2.6.16-rc5/linux rootfstype=hostfs rw \
init=/home/landley/busybox/busybox/testsuite/mount.testroot \
TESTDIR=/home/landley/busybox/busybox/testsuite COMMAND=./mount quiet

Rob
-- 
Never bet against the cheap plastic solution.

[-- Attachment #2: mounttests.tgz --]
[-- Type: application/x-tgz, Size: 3763 bytes --]

  parent reply	other threads:[~2006-03-14 16:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14  3:18 How do I get the ext3 driver to shut up? Rob Landley
2006-03-14  3:30 ` Randy.Dunlap
2006-03-14 14:11   ` j4K3xBl4sT3r
2006-03-14 15:20   ` Rob Landley [this message]
2006-03-14 17:26     ` Randy.Dunlap
2006-03-14  7:14 ` Andrew Morton
2006-03-14 12:59   ` [PATCH] Fix backwards meaning of MS_VERBOSE Theodore Ts'o
2006-03-14 14:48   ` How do I get the ext3 driver to shut up? Theodore Ts'o
2006-03-14 16:41     ` Rob Landley
2006-03-14 20:09       ` Theodore Ts'o
2006-03-14 16:32   ` Rob Landley

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=200603141020.27963.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.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