From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: hughd@google.com
Cc: tim.c.chen@linux.intel.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [2.6.36-rc1] List corruption when using initrd.
Date: Wed, 18 Aug 2010 10:13:33 +0900 [thread overview]
Message-ID: <201008180113.o7I1DXg6077317@www262.sakura.ne.jp> (raw)
In-Reply-To: <alpine.LSU.2.00.1008171523270.2106@sister.anvils>
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
"[2.6.36-rc1] Bugs in __free_pipe_info()".
> 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.
next prev parent reply other threads:[~2010-08-18 1:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 5:17 Tetsuo Handa
2010-08-17 7:51 ` Tetsuo Handa
2010-08-17 22:23 ` Hugh Dickins
2010-08-18 1:13 ` Tetsuo Handa [this message]
2010-08-18 3:28 ` Hugh Dickins
2010-08-18 3:32 ` [PATCH] shmem: fix percpu_counters list corruption Hugh Dickins
2010-08-18 16:50 ` Tim Chen
2010-08-18 4:09 ` [2.6.36-rc1] List corruption when using initrd Tetsuo Handa
2010-08-20 19:14 ` Paul E. McKenney
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=201008180113.o7I1DXg6077317@www262.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®