Linux NFS development
 help / color / mirror / Atom feed
From: Aaron Straus <aaron-bYFJunmd+ZV8UrSeD/g0lQ@public.gmane.org>
To: Carsten Aulbert
	<carsten.aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: kernel BUG at kernel/workqueue.c:291
Date: Tue, 3 Mar 2009 12:41:26 -0800	[thread overview]
Message-ID: <20090303204125.GB28232@merfinllc.com> (raw)
In-Reply-To: <49AD4B55.5060504-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>

Hi Carsten,

On Mar 03 04:23 PM, Carsten Aulbert wrote:
> > struct rpc_task does admittedly share storage for the work queue and the
> > rpc wait queue links, but if that were to be causing the reported
> > corruption, then it would mean that an rpc_task is simultaneously on a
> > wait queue and trying to execute on a work queue. I have no history of
> > that ever having happened.
> 
> Anything I might be able to give to you helping you to narrow it down
> somewhat? As written I suspect a certain type of user jobs, but since
> literally 1000s of these ran over the course of several days it might be
> hard to trigger this reliably again.

Out of curiosity, do you know (approximately) the last kernel you ran
which did not show the BUG?

i.e. we know 2.6.27.14 is bad, what was the last known good kernel?

Thanks!

				=a=


-- 
===================
Aaron Straus
aaron-bYFJunmd+ZV8UrSeD/g0lQ@public.gmane.org

  parent reply	other threads:[~2009-03-03 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49A84376.6030800@aei.mpg.de>
     [not found] ` <49ABBA44.1060302@aei.mpg.de>
     [not found]   ` <49ABBA44.1060302-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2009-03-03  7:26     ` kernel BUG at kernel/workqueue.c:291 Andrew Morton
2009-03-03  7:36       ` Carsten Aulbert
2009-03-03 15:16       ` Trond Myklebust
     [not found]         ` <1236093413.9631.58.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-03 15:23           ` Carsten Aulbert
     [not found]             ` <49AD4B55.5060504-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2009-03-03 20:41               ` Aaron Straus [this message]
2009-03-03 21:21               ` Trond Myklebust

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=20090303204125.GB28232@merfinllc.com \
    --to=aaron-byfjunmd+zv8ursed/g0lq@public.gmane.org \
    --cc=akpm@linux-foundation.org \
    --cc=carsten.aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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