From: Jens Axboe <axboe@suse.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: rwhron@earthlink.net, Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net
Subject: Re: fsync02 test hangs 2.5.1-pre3 + patch
Date: Thu, 29 Nov 2001 08:05:22 +0100 [thread overview]
Message-ID: <20011129080522.C5788@suse.de> (raw)
In-Reply-To: <20011129004851.A113@earthlink.net> <Pine.GSO.4.21.0111290050250.9516-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0111290050250.9516-100000@weyl.math.psu.edu>
On Thu, Nov 29 2001, Alexander Viro wrote:
>
>
> On Thu, 29 Nov 2001 rwhron@earthlink.net wrote:
>
> > On Thu, Nov 29, 2001 at 12:18:59AM -0500, rwhron@earthlink.net wrote:
> > > > c) 2.5.1-pre3 + fs/super.c from 2.5.1-pre2
> > > > (fs/super.c changes are independent from everything else).
> > >
> > > I'll try option c and let you know what happens.
> >
> > I ran the fsync02 test by itself, and that went fine. When I started
> > the "runalltests", the system locked up when "tail -f" showed fsync02.
> > It's possible that one of the next tests, fsync03 or ftruncate01 are
> > the actual triggers for the "can't write" lockup.
>
> OK, so what we have is breakage in bio parts merged in -pre3 _or_ breakage
> going back to -pre2. If you could rerun these tests for vanilla 2.5.1-pre2
> and see if they break...
-pre3 breakage is very possible, let me drink a cup of coffee and take a
closer look at this.
--
Jens Axboe
next prev parent reply other threads:[~2001-11-29 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 2:24 fsync02 test hangs 2.5.1-pre3 + patch rwhron
2001-11-29 2:32 ` Alexander Viro
2001-11-29 3:03 ` rwhron
2001-11-29 4:12 ` Alexander Viro
2001-11-29 5:18 ` rwhron
2001-11-29 5:48 ` rwhron
2001-11-29 6:04 ` Alexander Viro
2001-11-29 7:05 ` Jens Axboe [this message]
2001-11-29 7:17 ` Alexander Viro
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=20011129080522.C5788@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=rwhron@earthlink.net \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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.