From: Nathan Scott <nathans@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: linux-xfs@oss.sgi.com
Subject: Re: kernel BUG at fs/direct-io.c:916!
Date: Mon, 27 Mar 2006 08:08:11 +1000 [thread overview]
Message-ID: <20060327080811.D753448@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20060326184644.GC4776@charite.de>; from Ralf.Hildebrandt@charite.de on Sun, Mar 26, 2006 at 08:46:44PM +0200
On Sun, Mar 26, 2006 at 08:46:44PM +0200, Ralf Hildebrandt wrote:
> * Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>:
> > Today I wanted to run xfs_fsr on my laptop. I got:
>
> It's a 2.6.16-mm1 issue, since 2.6.16-git11 does not exhibit that
> failure.
>
> > Linux knarzkiste 2.6.16-mm1 #1 PREEMPT Fri Mar 24 19:01:24 CET 2006 i686 GNU/Linux
Hmm, there were XFS patches in -mm last week, but they also got
merged to mainline last week, not clear whether your git kernel
had those changes or not. I think there's probably some direct
I/O (generic) changes in -mm too based on list traffic from the
last couple of weeks (I'm an -mm lamer, sorry, couldn't easily
tell you exactly what patches those might be) - could you retry
with todays git snapshot and see if mainline is affected? Else
we'll need to find and analyse any -mm fs/direct-io.c patches.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-03-26 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060326230206.06C1EE083AAB@knarzkiste.dyndns.org>
2006-03-26 18:04 ` Ralf Hildebrandt
2006-03-26 18:46 ` Ralf Hildebrandt
2006-03-26 22:08 ` Nathan Scott [this message]
2006-03-26 23:03 ` Ralf Hildebrandt
2006-03-27 5:33 ` Nathan Scott
[not found] ` <20060327060436.GC2481@frodo>
[not found] ` <20060327110342.GX21946@charite.de>
2006-03-28 5:01 ` Nathan Scott
2006-03-28 11:28 ` Ralf Hildebrandt
2006-03-28 21:43 ` Nathan Scott
2006-03-29 8:35 ` Ralf Hildebrandt
2006-03-28 17:30 ` Badari Pulavarty
2006-03-28 22:23 ` Nathan Scott
2006-03-30 18:42 ` Badari Pulavarty
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=20060327080811.D753448@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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
all inboxes | Powered by JetHome®