From: Nathan Scott <nathans@sgi.com>
To: jesper.juhl@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078
Date: Fri, 4 Aug 2006 20:05:50 +1000 [thread overview]
Message-ID: <20060804200549.A2414667@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <9a8748490608040122l69ff139dtaae27e8981022dae@mail.gmail.com>; from jesper.juhl@gmail.com on Fri, Aug 04, 2006 at 10:22:21AM +0200
On Fri, Aug 04, 2006 at 10:22:21AM +0200, Jesper Juhl wrote:
> I just hit a BUG that looks XFS related.
>
> The machine is running 2.6.18-rc3-git3
>
> (more info below the BUG messages)
>
Thanks for reporting, Jesper - is it reproducible? Could you try this
patch for me? We had a couple of other reports of this, but the earlier
reporters have vanished ... could you let me know if this helps?
cheers.
--
Nathan
--- fs/xfs/xfs_alloc.c.orig 2006-08-04 20:00:34.333456250 +1000
+++ fs/xfs/xfs_alloc.c 2006-08-04 20:00:50.586472000 +1000
@@ -1949,14 +1949,8 @@ xfs_alloc_fix_freelist(
* the restrictions correctly. Can happen for free calls
* on a completely full ag.
*/
- if (targs.agbno == NULLAGBLOCK) {
- if (!(flags & XFS_ALLOC_FLAG_FREEING)) {
- xfs_trans_brelse(tp, agflbp);
- args->agbp = NULL;
- return 0;
- }
+ if (targs.agbno == NULLAGBLOCK)
break;
- }
/*
* Put each allocated block on the list.
*/
next parent reply other threads:[~2006-08-04 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9a8748490608040122l69ff139dtaae27e8981022dae@mail.gmail.com>
2006-08-04 10:05 ` Nathan Scott [this message]
2006-08-04 10:43 ` 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078 Jesper Juhl
[not found] <3aa654a40608072039r2b5c5a19hbd3e68e4fee40869@mail.gmail.com>
[not found] ` <20060808134438.E2526901@wobbly.melbourne.sgi.com>
[not found] ` <9a8748490608080137k596a6290r3567096668449a64@mail.gmail.com>
[not found] ` <20060808185405.B2528231@wobbly.melbourne.sgi.com>
[not found] ` <9a8748490608100431m244207b1v9c9c5087233fcf3a@mail.gmail.com>
[not found] ` <20060811083546.B2596458@wobbly.melbourne.sgi.com>
[not found] ` <9a8748490608101544n29f863e7o7584ac64f1d4c210@mail.gmail.com>
[not found] ` <9a8748490608101552w12822fa6m415a5fb5537c744d@mail.gmail.com>
[not found] ` <9a8748490608110133v5f973cf6w1af340f59bb229ec@mail.gmail.com>
[not found] ` <9a8748490608110325k25c340e2yac925eb226d1fe4f@mail.gmail.com>
2006-08-14 2:00 ` Nathan Scott
2006-08-14 7:49 ` Jesper Juhl
2006-08-15 9:03 ` Nathan Scott
2006-08-15 11:42 ` Jesper Juhl
2006-08-16 1:26 ` Nathan Scott
2006-08-17 21:23 ` Jesper Juhl
2006-08-15 14:37 ` Chris Wedgwood
2006-08-15 14:47 ` Jan Engelhardt
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=20060804200549.A2414667@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=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