From: Christoph Hellwig <hch@infradead.org>
To: Mikael Wahlberg <mikael.wahlberg@ardendo.se>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
"Per Lejontand" <pele@ardendo.se>,
"Jonas Engström" <jonas@ardendo.se>
Subject: Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!)
Date: Mon, 23 Feb 2004 13:13:31 +0000 [thread overview]
Message-ID: <20040223131331.A8778@infradead.org> (raw)
In-Reply-To: <1077541689.1247.12.camel@harrier>; from mikael.wahlberg@ardendo.se on Mon, Feb 23, 2004 at 02:08:09PM +0100
On Mon, Feb 23, 2004 at 02:08:09PM +0100, Mikael Wahlberg wrote:
> If you need any more information please tell us, it is quite urgent for
> us, since we really don't want to go back to 2.4, the performance
> increase with 2.6 is really impressive (Except when it crashes :)
Can you check whether the small patch below gets rid of you problems?
It still wouldn't explain the JFS problems, though.
--- 1.59/fs/xfs/linux/xfs_aops.c Mon Feb 9 05:39:27 2004
+++ edited/fs/xfs/linux/xfs_aops.c Mon Feb 23 15:11:33 2004
@@ -1170,7 +1170,7 @@
if (!delalloc && !unwritten)
goto free_buffers;
- if (!(gfp_mask & __GFP_FS))
+ if ((gfp_mask & (__GFP_FS|__GFP_WAIT)) != (__GFP_FS|__GFP_WAIT))
return 0;
/* If we are already inside a transaction or the thread cannot
next prev parent reply other threads:[~2004-02-23 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 15:49 Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!) Mikael Wahlberg
2004-02-23 12:19 ` Christoph Hellwig
2004-02-23 13:08 ` Mikael Wahlberg
2004-02-23 13:13 ` Christoph Hellwig [this message]
2004-03-04 9:35 ` Mikael Wahlberg
2004-02-23 13:46 ` Seth Mos
2004-02-23 13:50 ` Mikael Wahlberg
2004-02-23 13:46 ` Mikael Wahlberg
[not found] ` <1077543963.1246.20.camel@harrier.lucky.linux.kernel>
2004-04-28 4:39 ` allocation failures with CBQ bandwidth limiting & high net use (was Re: Filesystem kernel hangup, 2.6.3 (bad: scheduling while atomic!)) Brad Allen
2004-04-28 5:42 ` Andrew Morton
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=20040223131331.A8778@infradead.org \
--to=hch@infradead.org \
--cc=jonas@ardendo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=mikael.wahlberg@ardendo.se \
--cc=pele@ardendo.se \
/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