>>
>> After reviewing the patch I found that it still wasn't quite right.
>>
>> The upshot being that we need to go through the test process again
>> (under load, I've tested locally), if possible. Would you be able
>> re-test with this new patch please?
>
> Any news on testing?
The patch you sent on May 25 has been working perfectly for 3 three
weeks on a heavily used system running a 3.1.7 kernel.
However, when I (blindly) incorporate that patch into a 3.4.2 kernel
things go south almost immediately. With tracebacks like the following:
--------------------------------------------------
kernel: INFO: rcu_sched self-detected stall on CPU { 0} (t=15000 jiffies)
kernel: Pid: 13287, comm: automount Tainted: G O 3.4.2-0cse.0 #3
kernel: Call Trace:
kernel: <IRQ> [<ffffffff8108e832>] __rcu_pending+0x192/0x4c0
kernel: [<ffffffff8108f488>] rcu_check_callbacks+0x98/0xe0
kernel: [<ffffffff81037e43>] update_process_times+0x43/0x80
kernel: [<ffffffff810668e8>] tick_sched_timer+0x58/0x150
kernel: [<ffffffff8104aa6a>] __run_hrtimer.isra.33+0x4a/0xd0
kernel: [<ffffffff8104b077>] hrtimer_interrupt+0xc7/0x1e0
kernel: [<ffffffff813c4bcc>] ? call_softirq+0x1c/0x30
kernel: [<ffffffff8101ba94>] smp_apic_timer_interrupt+0x64/0xa0
kernel: [<ffffffff813c4287>] apic_timer_interrupt+0x67/0x70
kernel: <EOI> [<ffffffff810fe6a7>] ? mntput_no_expire+0x27/0x140
kernel: [<ffffffff813bd3ed>] ? _raw_spin_lock+0x1d/0x30
kernel: [<ffffffff811c53f7>] autofs4_expire_indirect+0x2d7/0x410
kernel: [<ffffffff811c5b80>] ? autofs_dev_ioctl_askumount+0x30/0x30
kernel: [<ffffffff811c57b5>] autofs4_do_expire_multi+0xc5/0x100
kernel: [<ffffffff811c5b80>] ? autofs_dev_ioctl_askumount+0x30/0x30
kernel: [<ffffffff811c5b9a>] autofs_dev_ioctl_expire+0x1a/0x20
kernel: [<ffffffff811c6134>] _autofs_dev_ioctl+0x234/0x370
kernel: [<ffffffff810f6d16>] ? __d_free+0x46/0x70
kernel: [<ffffffff811c627e>] autofs_dev_ioctl+0xe/0x20
kernel: [<ffffffff810f3267>] do_vfs_ioctl+0x97/0x580
kernel: [<ffffffff810fe7df>] ? mntput+0x1f/0x30
kernel: [<ffffffff810e3dbe>] ? fput+0x15e/0x250
kernel: [<ffffffff810f379a>] sys_ioctl+0x4a/0x80
kernel: [<ffffffff813c3822>] system_call_fastpath+0x16/0x1b
--------------------------------------------------
The caveat is that I applied your patch to 3.4.2 without investigating
if there were other changes that might need to be made. And it
had to be done manually since there was an extra line of code in
3.4.2 that caused one patch chunk to fail.
So I'm not quite sure what advice to offer. But I certainly
appreciate your efforts.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
