Bug#697887: audit: name_count maxed, losing inode data

2013-01-10 Thread Ben Hutchings
On Fri, 2013-01-11 at 00:42 +0100, Thilo Six wrote: [...] > >> [7.844458] audit: name_count maxed, losing inode data: dev=00:06, > >> inode=5738 > >> [7.844462] audit: name_count maxed, losing inode data: dev=00:06, > >> inode=5625 > >> [7.844466] audit: name_count maxed, losing inode

Bug#697887: audit: name_count maxed, losing inode data

2013-01-10 Thread Jonathan Nieder
Thilo Six wrote: > No. Speaking openly i do not know what it is telling me at all. But reading > "losing inode data" got my attention so to say. Yeah. If nothing else, we should tone down the message, rate-limit it, and make it trigger only once per syscall. > Those messages happended during bo

Bug#697887: audit: name_count maxed, losing inode data

2013-01-10 Thread Thilo Six
Hello Jonathan, Excerpt from Jonathan Nieder: >> Version: 3.2.35-2 > [...] >> As you can see below i got a long list of those >> "audit: name_count maxed, losing inode data:" messages. > > Thanks for reporting. Compare . Yes, looks like the same thing. >> I as

Bug#697887: audit: name_count maxed, losing inode data

2013-01-10 Thread Jonathan Nieder
Hi Thilo, Thilo Six wrote: > Version: 3.2.35-2 [...] > As you can see below i got a long list of those > "audit: name_count maxed, losing inode data:" messages. Thanks for reporting. Compare . > I assume the patch that fixes this bug is this one included in v3.3-

Bug#697887: audit: name_count maxed, losing inode data

2013-01-10 Thread Thilo Six
Package: src:linux Version: 3.2.35-2 Severity: normal Tags: upstream patch Dear Maintainer, As you can see below i got a long list of those "audit: name_count maxed, losing inode data:" messages. According to: https://bugzilla.redhat.com/show_bug.cgi?id=445757#c67 ---[ Michal Schmidt ]