public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70 (virgin) hangs running SDET
Date: Tue, 10 Jun 2003 12:46:13 -0700	[thread overview]
Message-ID: <20030610124613.40e65da7.akpm@digeo.com> (raw)
In-Reply-To: <12190000.1055266471@flay>

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> OK, well backing out dcache_lock-vs-tasklist_lock-take-3.patch does
> indeed seem to fix the problem. It's done 5.5 whole cycles now, and
> still going strong.

Well that patch fixed a real bug.  It abviously added or exposed another
one though.  

I continue to wonder if that task_struct is scrogged.  There seem to be no
other processes holding the lock.

Might be interesting to give the below patch a run with memory debug
enabled.

Also spinlock debugging enabled.  It would be nice to run with preempt and
sleep-in-spinlock debugging enabled too, but I think preempt is broken on
NUMA?

(Anton had a patch which just enabled the beancounting which is needed for
might_sleep() effectiveness without turning on preempt, but it needs more
work for ia32)


diff -puN fs/proc/base.c~a fs/proc/base.c
--- 25/fs/proc/base.c~a	Tue Jun 10 12:40:44 2003
+++ 25-akpm/fs/proc/base.c	Tue Jun 10 12:42:01 2003
@@ -1374,6 +1374,11 @@ struct dentry *proc_pid_lookup(struct in
 
 	dentry->d_op = &pid_base_dentry_operations;
 
+	if (task->bite_me != 0) {
+		printk("corrupted task_struct: 0x%x\n", task->bite_me);
+		BUG();
+	}
+
 	spin_lock(&task->proc_lock);
 	task->proc_dentry = dentry;
 	d_add(dentry, inode);
diff -puN include/linux/sched.h~a include/linux/sched.h
--- 25/include/linux/sched.h~a	Tue Jun 10 12:40:44 2003
+++ 25-akpm/include/linux/sched.h	Tue Jun 10 12:40:44 2003
@@ -330,6 +330,8 @@ struct task_struct {
 	struct list_head run_list;
 	prio_array_t *array;
 
+	u32 bite_me;
+
 	unsigned long sleep_avg;
 	unsigned long last_run;
 

_


  reply	other threads:[~2003-06-10 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <60380000.1055188542@flay>
2003-06-09 21:08 ` 2.5.70 (virgin) hangs running SDET Andrew Morton
2003-06-10  5:27   ` Martin J. Bligh
2003-06-10 14:14   ` Martin J. Bligh
2003-06-10 17:34     ` Martin J. Bligh
2003-06-10 19:46       ` Andrew Morton [this message]
2003-06-10 20:01         ` William Lee Irwin III
2003-06-11  5:06         ` Martin J. Bligh
2003-06-11  5:21           ` Andrew Morton
2003-06-11 14:36             ` Martin J. Bligh
2003-06-09 20:21 Martin J. Bligh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030610124613.40e65da7.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox