Re: 2.6.24-rc4-mm1: some issues on sparc64

From: Andrew Morton <[email protected]>
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 2.6.24-rc4-mm1: some issues on sparc64
    • From: Andrew Morton <[email protected]>

• References:
  • 2.6.24-rc4-mm1
    • From: Andrew Morton <[email protected]>
  • Re: 2.6.24-rc4-mm1: some issues on sparc64
    • From: Mariusz Kozlowski <[email protected]>
  • Re: 2.6.24-rc4-mm1: some issues on sparc64
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: tipc_init(), WARNING: at arch/x86/mm/highmem_32.c:52, [2.6.24-rc4-git5: Reported regressions from 2.6.23]
• Next by Date: Re: tipc_init(), WARNING: at arch/x86/mm/highmem_32.c:52, [2.6.24-rc4-git5: Reported regressions from 2.6.23]
• Previous by thread: Re: 2.6.24-rc4-mm1: some issues on sparc64
• Next by thread: Re: 2.6.24-rc4-mm1: some issues on sparc64
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]