[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.00.1008172022140.2868@sister.anvils>
Date: Tue, 17 Aug 2010 20:28:39 -0700 (PDT)
From: Hugh Dickins <hughd@...gle.com>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
cc: hughd@...gle.com, tim.c.chen@...ux.intel.com,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [2.6.36-rc1] List corruption when using initrd.
On Wed, 18 Aug 2010, Tetsuo Handa wrote:
> Hugh Dickins wrote:
> > Thanks for reporting and bisecting. Certainly there's a bug in shmem
> > (that we ought to have caught long before it reached 36-rc1: sorry),
> > and it is probably the cause of your crashes; but it's possible there's
> > a similar bug elsewhere too, something else messing up the percpu_counters
> > list - so please check if the patch below really does fix it for you.
>
> This patch solved the list_add() corruption messages and
Great.
> "[2.6.36-rc1] Bugs in __free_pipe_info()".
That's good, but puzzling. I'll mention it in the patch comment, since
that's what you've found: but I've given up trying to understand how.
>
> > I notice your dmesg also showed fs/inode.c:692 unlock_new_inode()
> > warnings from get_cramfs_inode(): those would be unrelated, and
> > probably from Al Viro's recent changes in cramfs/inode.c - Cc'ed.
> unlock_new_inode() warnings remain after applying this patch.
>
> Thank you.
Bigger thanks to you. Patch to Linus follows.
Hugh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists