From: Nathan Scott <nathans@sgi.com>
To: Jan Dittmer <jdi@l4x.org>, kernel <linux@idccenter.cn>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS Bug null pointer dereference in xfs_free_ag_extent
Date: Mon, 31 Jul 2006 09:44:24 +1000 [thread overview]
Message-ID: <20060731094424.E2280998@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44CB1303.7010303@l4x.org>; from jdi@l4x.org on Sat, Jul 29, 2006 at 09:49:23AM +0200
Hi there,
On Sat, Jul 29, 2006 at 09:49:23AM +0200, Jan Dittmer wrote:
> kernel schrieb:
> > I have the same problem, but it seems not have a patch right now.
>
> No, I got zero feedback, but let's cc the correct
> mailing list. I also filed bug 6877 at kernel.org
>
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?
thanks.
--
Nathan
next prev parent reply other threads:[~2006-07-30 23:46 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 [this message]
[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
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=20060731094424.E2280998@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@idccenter.cn \
--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