Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758900AbZIPM12 (ORCPT ); Wed, 16 Sep 2009 08:27:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758873AbZIPM1Y (ORCPT ); Wed, 16 Sep 2009 08:27:24 -0400 Received: from mail2.shareable.org ([80.68.89.115]:54452 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758783AbZIPM1X (ORCPT ); Wed, 16 Sep 2009 08:27:23 -0400 Date: Wed, 16 Sep 2009 13:27:23 +0100 From: Jamie Lokier To: Evgeniy Polyakov Cc: Eric Paris , David Miller , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org, viro@zeniv.linux.org.uk, alan@linux.intel.com, hch@infradead.org, torvalds@linux-foundation.org Subject: Re: fanotify as syscalls Message-ID: <20090916122723.GE29359@shareable.org> References: <1252703626.2305.50.camel@dhcp231-106.rdu.redhat.com> <20090911212731.GA19901@shareable.org> <1252705902.2305.83.camel@dhcp231-106.rdu.redhat.com> <20090912094110.GB24709@ioremap.net> <20090914001759.GB30621@shareable.org> <20090914140720.GA8564@ioremap.net> <1252955295.2246.35.camel@dhcp231-106.rdu.redhat.com> <20090915201620.GB32192@ioremap.net> <1253051699.5213.18.camel@dhcp231-106.rdu.redhat.com> <20090916120523.GA12830@ioremap.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090916120523.GA12830@ioremap.net> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1115 Lines: 28 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/