From: Andrew Morton <akpm@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>, Eric Paris <eparis@redhat.com>
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 19932] New: Getting lots of name_count maxed, losing inode data messages in /var/log/messages
Date: Mon, 11 Oct 2010 14:34:00 -0700 [thread overview]
Message-ID: <20101011143400.565facf5.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-19932-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 9 Oct 2010 06:58:14 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=19932
>
> Summary: Getting lots of name_count maxed, losing inode data
> messages in /var/log/messages
> Product: Other
> Version: 2.5
> Kernel Version: 2.6.35.7
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: other_other@kernel-bugs.osdl.org
> ReportedBy: jd1008@gmail.com
> Regression: No
>
>
> This old problem was also reported in redhat in redhat bugzilla:
> https://bugzilla.redhat.com/show_bug.cgi?id=445757
> in mid 2008.
>
>
> The message is coming from kernel/auditsc.c in audit_inc_name_count():
>
>
> static int audit_inc_name_count(struct audit_context *context,
> const struct inode *inode)
> {
> if (context->name_count >= AUDIT_NAMES) {
> if (inode)
> printk(KERN_DEBUG "audit: name_count maxed, losing
> inode data: "
> "dev=%02x:%02x, inode=%lu\n",
> MAJOR(inode->i_sb->s_dev),
> MINOR(inode->i_sb->s_dev),
> inode->i_ino);
>
> else
> printk(KERN_DEBUG "name_count maxed, losing inode
> data\n");
> return 1;
> }
> context->name_count++;
> #if AUDIT_DEBUG
> context->ino_count++;
> #endif
> return 0;
> }
>
> I wish the kernel would also dump the stack, and funcs param values into
> /var/log/messages
> so a user can take a look at the source and do some searching
> for the cause of this.
>
> Also, if you can advise on how I can rebuild the kernel so that
> it will drop into the debugger when this happens, would be a great
> help.
>
next parent reply other threads:[~2010-10-11 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19932-10286@https.bugzilla.kernel.org/>
2010-10-11 21:34 ` Andrew Morton [this message]
2010-10-11 21:42 ` [Bugme-new] [Bug 19932] New: Getting lots of name_count maxed, losing inode data messages in /var/log/messages Eric Paris
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=20101011143400.565facf5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).