| 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
| ||
|
Date: Wed, 16 Sep 2009 13:27:23 +0100 From: Jamie Lokier <jamie@...reable.org> To: Evgeniy Polyakov <zbr@...emap.net> Cc: Eric Paris <eparis@...hat.com>, David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, netdev@...r.kernel.org, viro@...iv.linux.org.uk, alan@...ux.intel.com, hch@...radead.org, torvalds@...ux-foundation.org Subject: Re: fanotify as syscalls Evgeniy Polyakov wrote: > It all sounds good and simple, but what if you will need modify command > with new arguments? Instead of adding new typed option you will need to > add another syscall. I already did that for inotify but via ioctl and > pretty sure there will be such need for much wider fanotify some time in > the future. Ew, that's unpleasant (adding to inotify via ioctl). You're right, it's not easy to add new syscalls, but it's not that hard either. I'd forgotten about Linus' strace argument. That's a good one. Of course everything should be a syscall by that argument :-) And strace can trace some ioctls and setsockopts. (But it's never pretty to see isatty() showing in strace as SNDCTL_TMR_TIMEBASE :-) Strace never shows structure of reads and writes to devices, so although efficient (you can batch), it's not nice for tracing. -- Jamie -- 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/
Powered by blists - more mailing lists