From: ebiederm@xmission•com (Eric W. Biederman)
To: sedat.dilek@gmail•com
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Al Viro <viro@zeniv•linux.org.uk>
Subject: Re: linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?)
Date: Thu, 07 Feb 2013 03:14:30 -0800 [thread overview]
Message-ID: <87ip644bqh.fsf@xmission.com> (raw)
In-Reply-To: <CA+icZUWNXpta6PhVCMvEjZVTgi0H0AC4Ou+ysG+b5PMEF6kxXQ@mail.gmail.com> (Sedat Dilek's message of "Thu, 7 Feb 2013 11:42:40 +0100")
Sedat Dilek <sedat.dilek@gmail•com> writes:
> On Thu, Feb 7, 2013 at 11:20 AM, Sedat Dilek <sedat.dilek@gmail•com> wrote:
>> On Thu, Feb 7, 2013 at 10:38 AM, Sedat Dilek <sedat.dilek@gmail•com> wrote:
>>> On Thu, Feb 7, 2013 at 7:37 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>>>> Hi all,
>>>>
>>>> Changes since 20130206:
>>>>
>>>> Removed tree: kvmtool (still present via the tip tree)
>>>>
>>>> The block tree lost its build failure.
>>>>
>>>> The tip tree gained a conflict against the s390 tree.
>>>>
>>>> The kvm tree gained a conflict against Linus' tree.
>>>>
>>>> The tty tree lost its build failure.
>>>>
>>>> The arm-soc tree gained conflicts against the iommu tree.
>>>>
>>>> The signal tree gained a conflict against the s390 tree.
>>>>
>>>> The akpm tree gained a conflict against the kvm tree and lost its build
>>>> failure.
>>>>
>>>> ----------------------------------------------------------------------------
>>>>
>>>
>>> My build-script uses fakeroot and does no more start:
>>>
>>> $ ./scripts/build_linux-next.sh
>>> make options ...... CC=gcc-4.6 -j4
>>> KBUILD_BUILD_USER=sedat.dilek@gmail•com
>>> LOCALVERSION=-next20130207-2-iniza-small
>>> dep-pkg options ... KDEB_PKGVERSION=3.8.0~rc6~next20130207-2~iniza+dileks1
>>> fakeroot, while creating message channels: Invalid argument
>>> This may be due to a lack of SYSV IPC support.
>>> fakeroot: error while starting the `faked' daemon.
>>> kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec
>>> ... or kill -l [sigspec]
>>>
>>>
>>> Any hints?
>>> ( I could run strace... )
>>>
>>> - Sedat -
>>
>> Attached strace outputs within yesterday's (GOOD) and today's (BAD) Linux-Next.
>>
>> - Sedat -
>
> [ CCing Al and Eric ]
>
> I compared quickly the diff between the -next versions and saw changes
> coming from signal and userns trees.
> ( Sorry for re-attaching the strace outputs. )
It has been about a week and a half since I have pushed anything into
the userns tree, and I don't have anything ipc related in my tree.
So the reason for the suspicion seems odd.
The straces are useless because all they show is that fakeroot was
forked, but there is not a trace of fakeroot itself.
Given the timing my initial suspect would be the idr_preload patches
from Tejun that were merged via Andrew's akpm tree. I didn't see
anything in there that would kill ipc but that is likely the most recent
touch to the ipc code.
Eric
next prev parent reply other threads:[~2013-02-07 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 9:38 linux-next: Tree for Feb 7 (fakeroot BROKEN due to SYSV IPC support?) Sedat Dilek
2013-02-07 10:20 ` Sedat Dilek
2013-02-07 10:42 ` Sedat Dilek
2013-02-07 11:14 ` Eric W. Biederman [this message]
2013-02-07 11:52 ` Sedat Dilek
2013-02-07 13:39 ` Sedat Dilek
2013-02-07 14:40 ` Sedat Dilek
2013-02-07 16:14 ` [PATCH v2] ipc: convert to idr_alloc() Tejun Heo
2013-02-07 19:15 ` Sedat Dilek
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=87ip644bqh.fsf@xmission.com \
--to=ebiederm@xmission$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sedat.dilek@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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