linux-kernel - Re: [PATCH] Re: name_count maxed, losing inode data: dev=00:05, inode=5221

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1266424679.9304.3.camel@localhost>
Date:	Wed, 17 Feb 2010 11:37:59 -0500
From:	Eric Paris <eparis@...hat.com>
To:	Christian Kujau <lists@...dbynature.de>
Cc:	LKML <linux-kernel@...r.kernel.org>, sandeen@...hat.com,
	Ralf.Hildebrandt@...rite.de, Udo.Wolter@...rite.de,
	ext-users <ext3-users@...hat.com>
Subject: Re: [PATCH] Re: name_count maxed, losing inode data: dev=00:05,
 inode=5221

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

--
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/