mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 13:09:51 +0900	[thread overview]
Message-ID: <201008180409.o7I49pof033727@www262.sakura.ne.jp> (raw)
In-Reply-To: <alpine.LSU.2.00.1008172022140.2868@sister.anvils>

Hugh Dickins wrote:
> > "[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.

Yeah, it's puzzling. What I was doing is

  ./newns ./foo | grep -vF OK

where "./newns" calls mount("tmpfs") after clone(CLONE_NEWNS)
and ./foo calls chroot()/mount("tmpfs")/umount()/pivot_root() etc.

After applying your patch, I can no longer reproduce __free_pipe_info() errors.
I don't know why __free_pipe_info() errors are reported on "grep" rather than
"newns" or "foo". But if the cause of __free_pipe_info() errors was memory
corruption by the bug in shmem, it is possible that fixing the bug in shmem
solves __free_pipe_info() errors.

Thanks.

  parent reply	other threads:[~2010-08-18  4:10 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
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         ` Tetsuo Handa [this message]
2010-08-20 19:14 ` [2.6.36-rc1] List corruption when using initrd 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=201008180409.o7I49pof033727@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
Powered by JetHome