From: Wu Fengguang <fengguang.wu@intel.com>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.2.0-rc5 NULL dereference BUG
Date: Thu, 5 Jan 2012 10:25:25 +0800 [thread overview]
Message-ID: <20120105022525.GA9408@localhost> (raw)
In-Reply-To: <CAGBYx2ZyiKrbsQmiC3YxB7sKjhEQVeznUM2cGrXMyQuXPZ5o1Q@mail.gmail.com>
On Thu, Jan 05, 2012 at 10:23:13AM +0800, Yongqiang Yang wrote:
> Hi Fengguang,
>
> > [ 646.051405] ffff880004ee1978 0000000000000000 0000000000000170 0000000000000000
> > [ 646.051405] Call Trace:
> > [ 646.051405] [<ffffffff81099aa3>] ? sched_clock_local+0x12/0x75
> > [ 646.051405] [<ffffffff810a5a16>] lock_acquire+0xdd/0x10a
> > [ 646.051405] [<ffffffff81175de4>] ? create_empty_buffers+0x4a/0xc1
> > [ 646.051405] [<ffffffff8199f623>] _raw_spin_lock+0x36/0x69
> > [ 646.051405] [<ffffffff81175de4>] ? create_empty_buffers+0x4a/0xc1
> > [ 646.051405] [<ffffffff81175de4>] create_empty_buffers+0x4a/0xc1
> > [ 646.051405] [<ffffffff811efd2f>] ext4_discard_partial_page_buffers_no_lock+0x9f/0x406
> > [ 646.051405] [<ffffffff8199ffeb>] ? _raw_spin_unlock+0x2b/0x2f
> > [ 646.051405] [<ffffffff81170c26>] ? __mark_inode_dirty+0x1ac/0x1cc
> > [ 646.051405] [<ffffffff811767f3>] ? generic_write_end+0x6d/0x7f
> > [ 646.051405] [<ffffffff811f15e5>] ext4_da_write_end+0x244/0x2ed
> > [ 646.051405] [<ffffffff810ffeec>] generic_file_buffered_write+0x183/0x22d
> It seems that you are running in to several problems related to
> discard_page_buffers_no_lock in write_end. The problems had been
> fixed by following patches [ext4: avoid potential hang in
> mpage_submit_io() when blocksize < pagesize], [ext4: correctly handle
> pages w/o buffers in ext4_discard_partial_buffers()] and [ext4: handle
> EOF correctly in ext4_bio_write_page()]. The patches had been merged
> to rc6.
That's great! I'll test rc7+.
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-05 2:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 5:54 3.2.0-rc5 NULL dereference BUG Wu Fengguang
2011-12-18 6:30 ` Wu Fengguang
2011-12-18 7:17 ` Yongqiang Yang
2011-12-18 11:32 ` Wu Fengguang
2012-01-05 1:56 ` Wu Fengguang
2012-01-05 2:23 ` Yongqiang Yang
2012-01-05 2:25 ` Wu Fengguang [this message]
[not found] ` <20120105023424.GA12242@localhost>
[not found] ` <CAGBYx2ZuL3j-T5nPermw3GZz4AWf-FsWcdj1+CT10TLAZBdUqw@mail.gmail.com>
[not found] ` <20120105024312.GA13069@localhost>
[not found] ` <CAGBYx2bP-ES0eg6KdfJFAfd4cNw61RDhWz=vHE-mTKFCVWwMHQ@mail.gmail.com>
2012-01-08 14:06 ` Wu Fengguang
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=20120105022525.GA9408@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaoqiangnk@gmail.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;
as well as URLs for NNTP newsgroup(s).