From: Nathan Scott <nathans@sgi.com>
To: Joe Jin <lkmaillist@gmail.com>, "Tony.Ho" <linux@idccenter.cn>,
jdi@l4x.org, Chris Seufert <seufert@gmail.com>
Cc: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: XFS Bug null pointer dereference in xfs_free_ag_extent
Date: Tue, 8 Aug 2006 13:30:05 +1000 [thread overview]
Message-ID: <20060808133005.C2526901@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <215036450607311849o43b1555br13ea2f3f20fb3b82@mail.gmail.com>; from lkmaillist@gmail.com on Tue, Aug 01, 2006 at 09:49:12AM +0800
On Tue, Aug 01, 2006 at 09:49:12AM +0800, Joe Jin wrote:
> >From the information, I think it caused by (args.agbp == NULL).
> get rid of, we'll find the call trace should panic:
> xfs_free_extent
> |_ xfs_free_ag_extent => here args.agbp= NULL;
> |_ xfs_btree_init_cursor()
> |_ agf = XFS_BUF_TO_AGF(agbp); => (xfs_agf_t
> *)XFS_BUF_PTR(arbp)
> |_ (xfs_caddr_t)((agbp)->b_addr) : but here,
> agbp is NULL
> so it caused the oops.
You've all reported this same issue - could any/all of you
try the patch here...
http://oss.sgi.com/archives/xfs/2006-08/msg00054.html
Let me know if that fixes it. In particular, if you were able
to easily reproduce this before, I'd like to hear whether this
resolves things, as I've still not hit the bug myself.
cheers.
--
Nathan
prev parent reply other threads:[~2006-08-08 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44BF29CD.1000809@l4x.org>
[not found] ` <44CB0BF7.6030204@idccenter.cn>
2006-07-29 7:49 ` XFS Bug null pointer dereference in xfs_free_ag_extent Jan Dittmer
2006-07-30 23:44 ` Nathan Scott
[not found] ` <44CDA156.6000105@idccenter.cn>
[not found] ` <20060731165522.K2280998@wobbly.melbourne.sgi.com>
[not found] ` <44CDB135.8080401@idccenter.cn>
[not found] ` <20060731194310.A2301615@wobbly.melbourne.sgi.com>
[not found] ` <44CDD5B9.8020608@idccenter.cn>
[not found] ` <215036450607311849o43b1555br13ea2f3f20fb3b82@mail.gmail.com>
[not found] ` <44CF0CDE.2080500@l4x.org>
2006-08-02 1:26 ` Nathan Scott
2006-08-08 3:30 ` Nathan Scott [this message]
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=20060808133005.C2526901@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@idccenter.cn \
--cc=lkmaillist@gmail.com \
--cc=seufert@gmail.com \
--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