From: Eric Paris <eparis@redhat.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
sandeen@redhat.com, Ralf.Hildebrandt@charite.de,
Udo.Wolter@charite.de, ext-users <ext3-users@redhat.com>
Subject: Re: [PATCH] Re: name_count maxed, losing inode data: dev=00:05, inode=5221
Date: Wed, 17 Feb 2010 11:37:59 -0500 [thread overview]
Message-ID: <1266424679.9304.3.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.2.01.1002080037480.27799@bogon.housecafe.de>
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
prev parent reply other threads:[~2010-02-17 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 17:39 [PATCH] Re: name_count maxed, losing inode data: dev=00:05, inode=5221 Christian Kujau
2010-02-08 8:38 ` Christian Kujau
2010-02-17 16:37 ` Eric Paris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1266424679.9304.3.camel@localhost \
--to=eparis@redhat.com \
--cc=Ralf.Hildebrandt@charite.de \
--cc=Udo.Wolter@charite.de \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox