From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752641Ab0BQQiX (ORCPT ); Wed, 17 Feb 2010 11:38:23 -0500 Received: from mx1.redhat.com ([209.132.183.28]:4292 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752127Ab0BQQiV (ORCPT ); Wed, 17 Feb 2010 11:38:21 -0500 Subject: Re: [PATCH] Re: name_count maxed, losing inode data: dev=00:05, inode=5221 From: Eric Paris To: Christian Kujau Cc: LKML , sandeen@redhat.com, Ralf.Hildebrandt@charite.de, Udo.Wolter@charite.de, ext-users In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Wed, 17 Feb 2010 11:37:59 -0500 Message-ID: <1266424679.9304.3.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2010-02-08 at 00:38 -0800, Christian Kujau wrote: > On Wed, 3 Feb 2010 at 09:39, Christian Kujau wrote: > > Ralf Hildebrandt reported[0] the following messages on ext3-users: > > > > name_count maxed, losing inode data: dev=00:05, inode=5221 > > > > because the filesystem in question is indeed ext3. However, this warning > > is not generated by ext3 code but by the audit framework. While the > > origins of these messages are discussed elsewhere[1] the following > > patch modifies the printks in question so that users know where these > > messages are coming from. There may be other places within the audit > > framework needing the same treatment. > > ...ping? I'm tracking these issues as Red Hat bz 445757. I've got a patch which removes the restriction of 20 inodes being accessed in one syscall which I've floated to Al Viro to see what he thinks. Since the restriction is gone we won't lose names and thus it removes these messages altogether. You are not forgotten! -Eric