linux-kernel - Re: [PATCH] MAINTAINERS: Add a guideline on notification of new userspace API/ABI elements

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 7 Mar 2011 15:43:55 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Joe Perches <joe@...ches.com>
Cc:	David Howells <dhowells@...hat.com>, mtk.manpages@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add a guideline on notification of new userspace API/ABI elements

On Monday 07 March 2011, Joe Perches wrote:
> Hey David.
> 
> Is there some list of files that are more likely to
> trigger this?
> 
> Maybe add a section like:
> 
> USERSPACE ABI/API INTERFACES
> L:      linux-api@...r.kernel.org
> F:      include/asm-generic/errno*.h
> F:      include/linux/capability.h
> F:      include/linux/compat.h
> F:      include/linux/syscalls.h
> F:      include/*/unistd.h

syscalls.h and compat.h are not really the user space ABI,
as user applications don't use those headers to link to
the kernel.

> Maybe add some arch wildcards?
> 
> F:      arch/*/include/asm/errno.h
> F:      arch/*/include/asm/unistd.h
> 
> Maybe add fs?
> 
> F:      fs/compat*.c
> 
> There's probably a bunch of others.
> Suggestions?
> 

I think you can add the entire asm-generic directory. The majority
of the changes in there are to exported files, so they impact
the ABI. For a specific list, you'd have to go through all the
files listed as exported in include/{linux,asm-generic}/Kbuild.

	Arnd
--
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/