[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#631799: [squeeze] Kernel logs "name_count maxed, losing inode data" messages



Hi,

On 12/07/2012 09:48 AM, Rik Theys wrote:
Hi,

On 12/06/2012 02:51 PM, Ben Hutchings wrote:
On Thu, 2012-12-06 at 13:58 +0100, Rik Theys wrote:
On 12/06/2012 01:29 PM, Ben Hutchings wrote:
It is not too difficult to fix up the conflicts.  But this is a
fairly
big change, so I think this bug should now be 'wontfix' for wheezy.
Sorry we didn't get it fixed earlier.

Sorry to hear that. Would a patch that simply increases the static
number of entries in the names array be an acceptable workaround? It
would decrease the change of hitting this bug.

Perhaps; do you have any idea what the limit should be?

What would you consider the upper limit to which we could increase the
number? Just so I know at which limit I can stop building test kernels.

Since you're asking me to make a somewhat arbitrary decision, I'll
arbitrarily decide on double the current limit, i.e. 40.

I've booted a kernel which has the AUDIT_NAMES set to 30. It's been
running for about 12 hours now without any messages (with the Debian
3.2.32 kernel it already logged the first message after 57s uptime).

The system is running the patches kernel for 5 days now without a single error message.

Is it possible to include this change in an upcoming 3.2 kernel upload?

Regards,

Rik

For now, it seems 30 is enough for my use case. If you're willing to
bump it up to 40, I would go for that.


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


Reply to: