From: Pavel Machek <pavel@ucw.cz>
To: koos vriezen <koos.vriezen@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.18 break scratchbox
Date: Sat, 7 Oct 2006 12:37:14 +0200 [thread overview]
Message-ID: <20061007103714.GD30034@elf.ucw.cz> (raw)
In-Reply-To: <d4e708d60610052341v8e8718cpfca5b60a28bfc93b@mail.gmail.com>
On Fri 2006-10-06 08:41:56, koos vriezen wrote:
> 2006/10/4, Pavel Machek <pavel@ucw.cz>:
> >Hi!
> >
> >> Hit by http://bugzilla.scratchbox.org/bugzilla/show_bug.cgi?id=279 I
> >> wondered why such
> >> a change that could break existing setups entered 2.6.18.
> >> Now I can peek through '/proc/<pid of process outside chroot env w/ my
> >> UID>/root' into the
> >> box's root (and that's why scratchbox is broken now).
> >
> >File bug at bugzilla.kernel.org :-).
> >
> >I'm afraid we did not know about this ABI change, and noone using
> >scratchbox tested 2.6.18-rcX...
>
> Well I did google for this before this report and eg.
> http://nchip.livejournal.com/ already mentioned it (but probably
> didn't report it at lkml) and there where some other links.
> But since I couldn't find any info on this new feature, that one can
> now read and write file through the /proc/xx/root link, I ask it here.
> And hopefully, if it's a regression, would be fixed in the stable tree
> ASAP. (Somehow I almost can't believe this change wouldn't show
> immediately in a regression test setup, and there must be a reason for
> opening this door w/o using an axe).
You probably want to do that bugzilla.kernel.org... and yes, this is
kind of bug I can imageine goes in without anyone noticing.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2006-10-07 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 14:59 koos vriezen
2006-10-04 21:35 ` Pavel Machek
2006-10-06 6:41 ` koos vriezen
2006-10-07 10:37 ` Pavel Machek [this message]
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=20061007103714.GD30034@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=koos.vriezen@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome