linux-kernel - Re: dmsetup fails on latest kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F1875CC.4010006@linux.intel.com>
Date:	Thu, 19 Jan 2012 11:58:04 -0800
From:	"H. Peter Anvin" <hpa@...ux.intel.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	"Kasatkin, Dmitry" <dmitry.kasatkin@...el.com>,
	device-mapper development <dm-devel@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: dmsetup fails on latest kernel

On 01/19/2012 11:05 AM, Linus Torvalds wrote:
>>
>> 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@...ux.intel.com>
>> 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
>
>    arch/x86/kernel/syscall_table_32.S
>
> and the new
>
>    arch/x86/syscalls/syscall_32.tbl
>
> 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?
>

Not off the top of my head.  I will try to reproduce this and see what 
the problem is.  Dmitry, what version of binutils and gcc are you using? 
  It could be that there is a toolchain problem.

	-hpa


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/