Skip to contentSkip to conversation

Don't trigger softlockup detector on network fs blocked tasks

PATCH New Andi Kleen 1 participant 1 message Aug 29, 2008

lore
Share & tools
lore

Andi Kleen

author
#0 lore raw

PATCH 1/1 Don't trigger softlockup detector on network fs blocked tasks

Don't trigger softlockup detector on network fs blocked tasks

Pulling the ethernet cable on a 2.6.27-rc system with NFS mounts currently leads to an ongoing flood of soft lockup detector backtraces for all tasks blocked on the NFS mounts when the hickup takes longer than 120s.

I don't think NFS problems should be all that noisy.

Luckily there's a reasonably easy way to distingush this case.

Don't report task softlockup warnings for tasks in TASK_KILLABLE state, which is used by the network file systems.

I believe this patch is a 2.6.27 candidate.

kernel/softlockup.c +4 -0
Index: linux-2.6.27-rc4-misc/kernel/softlockup.c
===================================================================
@@ -180,6 +180,10 @@ static void check_hung_task(struct task_
 	if (t->flags & PF_FROZEN)
 		return;
 
+	/* Don't check for tasks waiting on network file systems like NFS */
+	if (t->state & TASK_KILLABLE)
+		return;
+
 	if (switch_count != t->last_switch_count || !t->last_switch_timestamp) {
 		t->last_switch_count = switch_count;
 		t->last_switch_timestamp = now;