linux-ext4 - Re: [GIT PULL] ext4 changes for 3.15

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: <20140408134740.GB28822@thunk.org>
Date:	Tue, 8 Apr 2014 09:47:40 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Miklos Szeredi <miklos@...redi.hu>, Jan Kara <jack@...e.cz>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [GIT PULL] ext4 changes for 3.15

On Mon, Apr 07, 2014 at 10:25:30PM +0200, Geert Uytterhoeven wrote:
> > maintainers would have no idea that a new syscall has been added.
> 
> If i386 has the new syscall, scripts/checksyscalls.sh will catch it and
> inform us about it during our next kernel build.
> 
> If you add it to x86_64 only, bad luck for anyone else ;-)

Maybe we should change scripts/checksyscalls.sh to check the x86_64
list of syscalls, and not i386?

It's been a long time since "all the world's an i386" --- these days,
it's "all the world's an x86_64".  :-)

						- Ted

"Thou shalt foreswear, renounce, and abjure the vile heresy which
claimeth that ``All the world's a VAX'', and have no commerce with the
benighted heathens who cling to this barbarous belief, that the days
of thy program may be long even though the days of thy current machine
be short."  -- The Ten Commandments for C Programmers

- http://www.lysator.liu.se/c/ten-commandments.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html