From: Andrew Morton <akpm@zip.com.au>
To: Matt Bernstein <matt@theBachChoir.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops with 2.4.17 + mini-ll patch
Date: Thu, 10 Jan 2002 12:54:14 -0800 [thread overview]
Message-ID: <3C3DFF76.2DA2F5BD@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.43.0201101544330.31242-100000@nick.dcs.qmul.ac.uk>
Matt Bernstein wrote:
>
> Not sure if this is related to your patch (which looked harmless enough to
> me :), but here it is anyway.
mmm.. Probably coincidental.
> Dual PIII 1GHz, modular everything inc. ATA/IDE (VIA); SCSI (gdth.o);
> NFSv3 (udp, client only); autofs4; ext2 only for local fs. Debian woody.
It could be a timer deletion race. There are still zillions of these,
but nobody ever encounters them.
What was the system doing at the time? Do you think a module could
have been in the process of unloading? autofs unmount, something
like that?
-
next prev parent reply other threads:[~2002-01-10 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 15:52 oops with 2.4.17 + mini-ll patch Matt Bernstein
2002-01-10 20:54 ` Andrew Morton [this message]
2002-01-10 23:53 ` Matt Bernstein
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=3C3DFF76.2DA2F5BD@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@theBachChoir.org.uk \
/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