From mboxrd@z Thu Jan 1 00:00:00 1970 From: pg@aud.list.sabi.co.UK (Peter Grandi) Subject: Re: peculiar disappearance of most audit rules Date: Sun, 27 Apr 2014 21:33:34 +0100 Message-ID: <21341.27038.918993.838943@tree.ty.sabi.co.uk> References: <1806426.QoIu6KxFX5@x2> <21333.33865.378826.157120@tree.ty.sabi.co.uk> <21334.54971.174073.755376@tree.ty.sabi.co.uk> <21335.29725.410585.629604@tree.ty.sabi.co.uk> <1398263642.2596.23.camel@flatline.rdu.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (ext-mx16.extmail.prod.ext.phx2.redhat.com [10.5.110.21]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id s3RKXjFq003589 for ; Sun, 27 Apr 2014 16:33:45 -0400 Received: from anakin.london.02.net (anakin.london.02.net [87.194.255.134]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s3RKXgog023992 for ; Sun, 27 Apr 2014 16:33:43 -0400 Received: from ty.sabi.co.UK (94.194.168.220) by anakin.london.02.net (8.5.140) id 51DAA728052ACC8B for linux-audit@redhat.com; Sun, 27 Apr 2014 21:33:45 +0100 Received: from from [127.0.0.1] (helo=tree.ty.sabi.co.uk) by ty.sabi.co.UK with esmtp(Exim 4.76 #1) id 1WeVlX-0003Rp-2F for ; Sun, 27 Apr 2014 21:33:35 +0100 In-Reply-To: <1398263642.2596.23.camel@flatline.rdu.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Linux audit List-Id: linux-audit@redhat.com [ .... ] > What's the kernel in question? Ubuntu 12.04's 3.2 and SteamOS 3.10. > audit hasn't used "inotify" in a long time. We now use > "fsnotify". Out of laziness I used 'inotify' to mean both; also at one point I was looking at some 2.6.x sources as there seemed to be relevant changes in some mailing list. > but in either case, the inodes aren't supposed to be able to > be kicked out of core... But on 3 different system I have they really seem to be evicted, and with regularity, and this does not happen if the inodes are kept open. >>From the source I have looked at, the *notify code seems to attempt to hold on to the inodes that are watched, but perhaps it has some hidden assumptions that the 'audit' module does not satisfy.