Re: dmsetup fails on latest kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On Thu, Jan 19, 2012 at 7:56 AM, Kasatkin, Dmitry
<dmitry.kasatkin@xxxxxxxxx> wrote:
> On Thu, Jan 19, 2012 at 3:02 PM, Kasatkin, Dmitry
> <dmitry.kasatkin@xxxxxxxxx> wrote:
>> Hi,
>> (subject added)
>> I rebased on the stop of latest mainline tree and now dmsetup fails...
>> It says: "Failed to create notification semaphore: Function not implemented".
>> I run strace and saw that dmsetup uses "semget" which returns -ENOSYS...
>> It works on
>> 122804ecb59493fbb4d31b3ba9ac59faaf45276f
>> but does not work on
>> ccb19d263fd1c9e34948e2158c53eacbff369344
>> Any ideas?
>> - Dmitry
> Hi,
> I have bisected the problem...
> It is introduced by this commit:
> 303395ac3bf3e2cb488435537d416bc840438fcb is the first bad commit
> commit 303395ac3bf3e2cb488435537d416bc840438fcb
> Author: H. Peter Anvin <hpa@xxxxxxxxxxxxxxx>
> Date:   Fri Nov 11 16:07:41 2011 -0800
>    x86: Generate system call tables and unistd_*.h from tables

Interesting. I just munged the old pre-merge


and the new


with some trivial shell scripting, and they are definitely identical.

So the tables look like they match 1:1.

The compat tables match too, except the new list contains the entry
for bdflush (134), but that's a legacy thing that doesn't matter.

I wonder what else could be going on. Wrong number of system calls
check? Peter, any ideas?


dm-devel mailing list

[DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

Add to Google Powered by Linux