From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: m.kozlowski@tuxland.pl, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: 2.6.24-rc4-mm1: some issues on sparc64
Date: Sun, 09 Dec 2007 00:45:17 -0800 (PST) [thread overview]
Message-ID: <20071209.004517.201813773.davem@davemloft.net> (raw)
In-Reply-To: <20071208102239.2457eeaa.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Sat, 8 Dec 2007 10:22:39 -0800
> That's
>
> J_ASSERT_BH(bh, !buffer_jbddirty(bh));
>
> at the end of journal_unmap_buffer().
>
> I don't recall seeing that before and I can't think of anything we've
> done recently which could cause it, sorry.
If the per-cpu data patches are in the -mm tree that is the first
place I would start looking at for possible cause.
next prev parent reply other threads:[~2007-12-09 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071204211701.994dfce6.akpm@linux-foundation.org>
[not found] ` <200712081920.28748.m.kozlowski@tuxland.pl>
2007-12-08 18:22 ` 2.6.24-rc4-mm1: some issues on sparc64 Andrew Morton
2007-12-09 8:45 ` David Miller [this message]
2007-12-09 9:03 ` Andrew Morton
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=20071209.004517.201813773.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=sparclinux@vger.kernel.org \
/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