From: Olaf Hering <olaf@aepfle.de>
To: Shailabh Nagar <nagar@watson.ibm.com>
Cc: linux-kernel@vger.kernel.org, Balbir Singh <balbir@in.ibm.com>
Subject: Re: oops in __delayacct_blkio_ticks with 2.6.18-rc4
Date: Wed, 23 Aug 2006 13:18:15 +0200 [thread overview]
Message-ID: <20060823111815.GA11270@aepfle.de> (raw)
In-Reply-To: <44EB5684.60002@watson.ibm.com>
On Tue, Aug 22, Shailabh Nagar wrote:
> Olaf Hering wrote:
> > https://bugzilla.novell.com/show_bug.cgi?id=200526
> >
>
> Thanks for detecting this.
>
> I suspect the oops is caused by a reading of /proc/<tgid>/stat for some task
> that is late in exit. Currently tsk->delays is being freed up too early (before
> the tsk is removed from the tasklist).
>
> Could you try the patch below ? It was unclear from the bug what userspace
> actions were being done to reproduce the oops - I suspect some kind of
> reading of /proc/.../stat for all processes ?
I dont have a way to trigger it. The commands were 'w' and 'pstree'.
next prev parent reply other threads:[~2006-08-23 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 11:24 oops in __delayacct_blkio_ticks with 2.6.18-rc4 Olaf Hering
2006-08-22 19:09 ` Shailabh Nagar
2006-08-23 11:18 ` Olaf Hering [this message]
2006-08-24 19:05 ` Shailabh Nagar
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=20060823111815.GA11270@aepfle.de \
--to=olaf@aepfle.de \
--cc=balbir@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nagar@watson.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.