[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUXuw7QBn4CPLLuiVUjHin0m6GRdbczGw=bZY+Z60sXNow@mail.gmail.com>
Date: Fri, 21 Jun 2013 21:34:18 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Davidlohr Bueso <davidlohr.bueso@...com>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-mm <linux-mm@...ck.org>, Andi Kleen <andi@...stfloor.org>,
Rik van Riel <riel@...hat.com>,
Manfred Spraul <manfred@...orfullife.com>
Subject: Re: linux-next: Tree for Jun 21 [ BROKEN ipc/ipc-msg ]
On Fri, Jun 21, 2013 at 10:17 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Happy solstice!
>
> Changes since 20130620:
>
> Dropped tree: mailbox (really bad merge conflicts with the arm-soc tree)
>
> The net-next tree gained a conflict against the net tree.
>
> The leds tree still had its build failure, so I used the version from
> next-20130607.
>
> The arm-soc tree gained conflicts against the tip, net-next, mfd and
> mailbox trees.
>
> The staging tree still had its build failure for which I disabled some
> code.
>
> The akpm tree lost a few patches that turned up elsewhere and gained
> conflicts against the ftrace and arm-soc trees.
>
> ----------------------------------------------------------------------------
>
[ CC IPC folks ]
Building via 'make deb-pkg' with fakeroot fails here like this:
make: *** [deb-pkg] Terminated
/usr/bin/fakeroot: line 181: 2386 Terminated
FAKEROOTKEY=$FAKEROOTKEY LD_LIBRARY_PATH="$PATHS" LD_PRELOAD="$LIB"
"$@"
semop(1): encountered an error: Identifier removed
semop(2): encountered an error: Invalid argument
semop(1): encountered an error: Identifier removed
semop(1): encountered an error: Identifier removed
semop(1): encountered an error: Invalid argument
semop(1): encountered an error: Invalid argument
semop(1): encountered an error: Invalid argument
The issue is present since next-20130606!
LAST KNOWN GOOD: next-20130605
FIRST KNOWN BAD: next-20130606
KNOWN GOOD: next-20130604
KNOWN BAD: next-20130607 || next-20130619 || next-20130620 || next-20130621
git-bisect says CULPRIT commit is...
"ipc,msg: shorten critical region in msgrcv"
NOTE: msg_lock_(check_) routines have to be restored (one more revert needed)!
Reverting both (below) commits makes fakeroot build via 'make dep-pkg" again.
I have tested the revert-patches with next-20130606 and next-20130621
(see file-attachments).
My build-script is attached!
Can someone of the IPC folks look at that?
Thanks!
- Sedat -
P.S.: Commit-IDs listed below.
[ next-20130606 ]
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/?id=next-20130606
"ipc: remove unused functions"
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8793fdfb0d0a6ed5916767e29a15d3eb56e04e79
"ipc,msg: shorten critical region in msgrcv"
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c0ff93322847a54f74a5450032c4df64c17fdaed
[ next-20130621 ]
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/?id=next-20130621
"ipc: remove unused functions"
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=941ce57c81dcceadf55265616ee1e8bef18b0ad3
"ipc,msg: shorten critical region in msgrcv"
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=62190df4081ee8504e3611d45edb40450cb408ac
Download attachment "build_linux-next.sh" of type "application/x-sh" (3849 bytes)
Download attachment "3.10.0-rc4-next20130606-3-iniza-small.patch" of type "application/octet-stream" (6338 bytes)
Download attachment "3.10.0-rc6-next20130621-2-iniza-small.patch" of type "application/octet-stream" (7638 bytes)
Powered by blists - more mailing lists