All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels
Date: Sun, 10 Oct 2010 15:49:53 +0100	[thread overview]
Message-ID: <20101010144952.GF19804@ZenIV.linux.org.uk> (raw)
In-Reply-To: <AANLkTin4886D+-yo=zrf2Yj2R5NM9qdRkc3M9cG2rN_F@mail.gmail.com>

On Sun, Oct 10, 2010 at 11:47:20AM +0200, Geert Uytterhoeven wrote:
> > The cheapest way to reproduce is to boot with init=/bin/sh, then
> > mount /proc and have stat("/proc/2/exe", &st) called; if stat()
> > returns 0, we are fscked. ??The critical part is between return
> > from proc_exe_link() (we'll leave it via if (!mm) return -ENOENT;)
> > to return from __do_follow_link() -> do_follow_link() -> link_path_walk().
> 
> I booted 2.6.36-rc7-atari-00360-g0dd2e6a (my current private test kernel) with
> init=/bin/sh, mounted /proc, and tried
> 
>     for i in $(seq 1000); do stat /proc/2/exe; done
> 
> a few times, but I didn't see any ida_remove messages.
> It cannot read the /proc/2/exe symlink, though.
> 
> This is on aranym-0.9.9-1 from Ubuntu/amd64.

stat -L /proc/2/exec, otherwise you'll hit lstat() instead of stat().
And FWIW 0.9.10-1 squeeze/amd64 also triggers here...

  reply	other threads:[~2010-10-10 14:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 17:49 aranym bug, manifests as "ida_remove called for id=13" on recent kernels Al Viro
2010-10-10  9:47 ` Geert Uytterhoeven
2010-10-10 14:49   ` Al Viro [this message]
2010-10-10 20:18     ` Geert Uytterhoeven
2010-10-10 23:52       ` Al Viro
2010-10-11  2:41         ` Al Viro
2010-10-11  4:36           ` Brad Boyer
2010-10-11  4:48             ` Al Viro
2010-10-11 12:21               ` Thorsten Glaser
2010-10-11 12:21                 ` Thorsten Glaser
2010-10-11 13:10                 ` Andreas Schwab
2010-10-11 13:35                 ` Al Viro
2010-10-11 13:45                   ` Thorsten Glaser
2010-10-11 14:15                   ` Andreas Schwab
2010-10-11 14:24                     ` Al Viro
2010-10-11 22:02                       ` Al Viro
2010-11-02 15:30                       ` Geert Uytterhoeven
2010-10-11 19:05                 ` Mikael Pettersson
2010-10-11  9:27           ` Mikael Pettersson
2010-10-11 11:50             ` Mikael Pettersson
2010-10-11 12:29             ` Andreas Schwab
2010-10-11  8:39         ` Geert Uytterhoeven

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=20101010144952.GF19804@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.