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]
Date:	Fri, 11 Apr 2014 13:50:50 +0200
From:	Miklos Szeredi <>
To:	Russell King - ARM Linux <>
Cc:	linux-arch <>,
	Kernel Mailing List <>,
	Miklos Szeredi <>
Subject: Re: [PATCH 02/15] arm: __NR_syscalls fix

On Fri, Apr 11, 2014 at 12:33 PM, Russell King - ARM Linux
<> wrote:
> On Fri, Apr 11, 2014 at 12:25:38PM +0200, Miklos Szeredi wrote:
>> From: Miklos Szeredi <>
>> Signed-off-by: Miklos Szeredi <>
>> Cc: Russell King <>
>> ---
> This has me wondering...
> (a) what you think it fixes
> (b) whether you tried to build-test this
> The ARM instruction set supports 8-bit immediate constants with an even
> power of two shift.  384 fits that (0x180), 382 does not (0x17e), and
> in your following patch, 383 definitely doesn't (0x17f).
> Having this constant larger than necessary does not cause any problem
> for the syscall table: we explicitly pad it with calls to sys_ni_syscall
> to make up the difference.

Yes, and the padding will be of wrong length if NR_syscalls is
incorrect (which may be Oopsable?).  At least that is my impression
from a casual glance.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists