linux-kernel - Re: [PATCH v05 50/72] include/uapi/linux/fuse.h: use linux/types.h also in userspace

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]

Date:   Tue, 23 Aug 2016 10:39:58 +0300
From:   Mikko Rapeli <mikko.rapeli@....fi>
To:     Miklos Szeredi <miklos@...redi.hu>
Cc:     linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
        linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v05 50/72] include/uapi/linux/fuse.h: use linux/types.h
 also in userspace

On Tue, Aug 23, 2016 at 09:16:22AM +0200, Miklos Szeredi wrote:
> On Mon, Aug 22, 2016 at 8:33 PM, Mikko Rapeli <mikko.rapeli@....fi> wrote:
> > Kernel headers should not use stdint.h.
> >
> 
> NACK.
> 
> This header is used by more than one OS.   Having a different version
> for different OS's makes no sense, hence the choice of stdint.  We've
> been over this many times.  I'll do a patch with a big fat warning at
> the top of this header so that people don't spend time doing this
> useless conversion over and over again.

Yes, saw this coming. drm developers have the same problem.

Is there some way to define which kernel uapi headers are allowed to use
stdint.h definitions in userspace and which not?

-Mikko