From: Nathan Scott <nathans@sgi.com>
To: kernel <linux@idccenter.cn>
Cc: jdi@l4x.org, linux-kernel@vger.kernel.org
Subject: Re: XFS Bug null pointer dereference in xfs_free_ag_extent
Date: Mon, 31 Jul 2006 16:55:22 +1000 [thread overview]
Message-ID: <20060731165522.K2280998@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44CDA156.6000105@idccenter.cn>; from linux@idccenter.cn on Mon, Jul 31, 2006 at 02:21:10PM +0800
On Mon, Jul 31, 2006 at 02:21:10PM +0800, kernel wrote:
> Test again......very strange.
> I can easily reproduce it on the XFS with SAN(FLX380) connected with a
> qlogic 2400 FC card.
Eggshellent... can you reproduce it with each of those changes
(below) backed out of your tree please? Else, git bisect is our
next best bet. Thanks!
> > Is this easily reproducible for you? I've not seen it before, and
> > the only possibly related recent changes I can think of are these:
> >
> > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e63a3690013a475746ad2cea998ebb534d825704
> >
> > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d210a28cd851082cec9b282443f8cc0e6fc09830
> >
> > Could you try reverting each of those to see if either is the cause?
cheers.
--
Nathan
next prev parent reply other threads:[~2006-07-31 6:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 6:59 Jan Dittmer
2006-07-29 7:19 ` kernel
2006-07-29 7:49 ` Jan Dittmer
2006-07-29 8:10 ` kernel
2006-07-30 23:44 ` Nathan Scott
2006-07-31 1:30 ` kernel
2006-07-31 6:21 ` kernel
2006-07-31 6:55 ` Nathan Scott [this message]
2006-07-31 7:28 ` kernel
2006-07-31 8:41 ` Joe Jin
2006-07-31 9:53 ` Nathan Scott
2006-07-31 9:43 ` Nathan Scott
2006-07-31 10:04 ` kernel
[not found] ` <215036450607311849o43b1555br13ea2f3f20fb3b82@mail.gmail.com>
2006-08-01 8:12 ` Jan Dittmer
2006-08-02 1:26 ` Nathan Scott
2006-08-08 3:30 ` Nathan Scott
2006-07-31 6:58 ` Jan Dittmer
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=20060731165522.K2280998@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@idccenter.cn \
/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®