From: Chris Mason <chris.mason@fusionio.com>
To: David Sterba <dave@jikos.cz>
Cc: Tom Gundersen <teg@jklm.no>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [bug] oops in linux-3.8-rc2
Date: Mon, 7 Jan 2013 08:00:37 -0500 [thread overview]
Message-ID: <20130107130037.GA30947@shiny> (raw)
In-Reply-To: <20130107111037.GB12992@twin.jikos.cz>
On Mon, Jan 07, 2013 at 04:10:37AM -0700, David Sterba wrote:
> Hi,
>
> On Mon, Jan 07, 2013 at 01:51:21AM +0100, Tom Gundersen wrote:
> > I ran into a bug today with 3.8-rc2 [0], following an "make
> > modules_install && make install" of the kernel.
> >
> > I have been using the same kernel without problems for some days, the
> > only change immediately before the oops was that I switched from plain
> > partitions to using multi-device and subvolumes.
> >
> > [0]: <https://plus.google.com/114015603831160344127/posts/fzEYnF64NkZ>
>
> BUG at mm/page-writeback.c:2164
>
> 2160 int clear_page_dirty_for_io(struct page *page)
> 2161 {
> 2162 struct address_space *mapping = page_mapping(page);
> 2163
> 2164 BUG_ON(!PageLocked(page));
>
> btrfs on the stack is only __btrfs_buffered_write +
> btrfs_file_aio_write, ie. just a buffered write, originating from
> pwrite64.
>
> The bug_on condition is clear, the question is why the page is not
> locked.
The big question is, can you make it happen again?
-chris
next prev parent reply other threads:[~2013-01-07 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 0:51 [bug] oops in linux-3.8-rc2 Tom Gundersen
2013-01-07 11:10 ` David Sterba
2013-01-07 13:00 ` Chris Mason [this message]
2013-01-07 16:27 ` Tom Gundersen
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=20130107130037.GA30947@shiny \
--to=chris.mason@fusionio.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=teg@jklm.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.