On 11/25/2012 01:12 AM, Jonathan Nieder wrote:
On some of our servers, we periodically see "name_count maxed,
losing inode data" messages in the kernel log.
As you mentioned, this is said to be fixed by
commit 5195d8e217a7
Author: Eric Paris <epa...@redhat.com>
Date: Tue Jan 3 14:23:05 2012 -0500
audit: dynamically allocate audit_names when not enough
space is in the names array
which is part of 3.3.
Am I correct in understanding that the wheezy kernel is affected, too?
What is the impact of this bug --- does it flood logs in some
situations, for example, or does it lose important information? Is
the fix harmless or does it have potential downsides?
On this particular server, I get 3 messages every approx. 6 minutes.
[5262360.801855] name_count maxed, losing inode data: dev=00:07, inode=8
[5262360.801861] name_count maxed, losing inode data: dev=00:07,
inode=334434366
[5262360.803580] name_count maxed, losing inode data: dev=00:3c,
inode=21757958
The inode=8 and inode=21757958 are always the same. The second message
is always different.
I don't think it loses important information in my case as I don't audit
a lot of items. My audit log is 99% LOGIN audits.
I have not yet tried to apply the fix, so I can't comment on that.
I can install the 3.2 backports kernel on this system to see if Wheezy
is also affected, but I assume it is if the fix is in 3.3. It could be a
while before I can confirm this as this is a production system and I did
not plan on rebooting the system before the end of January. I'll see if
I can squeeze in a reboot somewhere.
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee
+32(0)16/32.11.07
----------------------------------------------------------------
<<Any errors in spelling, tact or fact are transmission errors>>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
