All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org,
	Lukasz Trabinski <lukasz@wsisiz.edu.pl>,
	Marc-Christian Petersen <m.c.p@wolk-project.de>,
	Jordan Breeding <jordan.breeding@attbi.com>,
	Matthew Wilcox <willy@debian.org>, Robert Love <rml@tech9.net>,
	Mikael Pettersson <mikpe@csd.uu.se>,
	Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5 Kernel Problem Reports as of 27 Sep
Date: Sat, 28 Sep 2002 02:46:34 +0100	[thread overview]
Message-ID: <20020928024634.C18377@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0209271833280.12092-100000@dad.molina>; from tmolina@cox.net on Fri, Sep 27, 2002 at 07:54:16PM -0500

On Fri, Sep 27, 2002 at 07:54:16PM -0500, Thomas Molina wrote:
>   17. http://marc.theaimsgroup.com/?l=linux-kernel&m=103237662509801&w=2
>    oops in lock_get_status                open               18 Sep 2002
> 
>   18. http://marc.theaimsgroup.com/?l=linux-kernel&m=103244657605155&w=2
>                                           additional reports 20 Sep 2002
> 
> Matthew Wilcox <willy@debian.org> requested debugging data and was working 
> on a fix.  What is the status of this?

I've been able to reproduce it (with ntop).  I think I know which change
broke it.  What I haven't been able to do is write a testcase which
reliably provokes it.  Help appreciated.

-- 
Revolutions do not require corporate support.

  parent reply	other threads:[~2002-09-28  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28  0:54 2.5 Kernel Problem Reports as of 27 Sep Thomas Molina
2002-09-28  1:17 ` Andrew Morton
2002-09-28  1:46 ` Matthew Wilcox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-30  0:10 Mikael Pettersson
2002-09-30 16:29 ` Alan Cox
2002-09-30 18:29   ` Thomas Molina

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=20020928024634.C18377@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=akpm@digeo.com \
    --cc=jordan.breeding@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz@wsisiz.edu.pl \
    --cc=m.c.p@wolk-project.de \
    --cc=mikpe@csd.uu.se \
    --cc=rml@tech9.net \
    --cc=tmolina@cox.net \
    /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.