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  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:	Sun, 17 Apr 2016 19:02:42 -0700
From:	"H. Peter Anvin" <>
To:	Greg KH <>
Cc:	"Theodore Ts'o" <>,
	Mathieu Desnoyers <>,
	"Richard W.M. Jones" <>,, Thomas Gleixner <>,, Andrew Morton <>,,, zab <>,,
	"Paul E. McKenney" <>,
	Andrea Arcangeli <>,,
	Pavel Emelyanov <>,,
	Milosz Tanski <>,
	rostedt <>,,, gorcunov <>,
	iulia manda21 <>,
	dave hansen <>,
	mguzik <>,,
	Davidlohr Bueso <>,
	linux-api <>,,, Linus Torvalds <>
Subject: Re: [PATCH v2 0/2] vfs: Define new syscall getumask.

On 04/17/16 18:09, Greg KH wrote:
>> There aren't a *lot* of such system calls, but even in that thread the
>> "oh, only two applications need this, let them use syscall(3)" seems to
>> remain.
> And only 2 applications will continue to use it because no one wants to
> write syscall() wrappers for their individual applications, so it's a
> vicious cycle :(
> I really like the 'libinux' idea, did anyone every hack up a first-pass
> at this?  And I'm guessing we have more syscalls now that would need to
> be added (like getrandom(), but that shouldn't be too difficult.

I haven't hacked anything up yet, but I think it would be easy to simply
take the klibc machinery, remove the stuff that isn't needed, and adjust
the handling of errno(3).  I think it is time I admit that it needs to
be put on my TODO list.


Powered by blists - more mailing lists