From: Stephen Crowley <stephenc@digitalpassage.com>
To: David Weinehall <tao@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs.c:567
Date: Sun, 29 Oct 2000 11:25:14 -0600 [thread overview]
Message-ID: <20001029112514.A20492@intolerance.digitalpassage.com> (raw)
In-Reply-To: <20001028184342.A1525@intolerance.digitalpassage.com> <20001029112758.B768@khan.acc.umu.se>
In-Reply-To: <20001029112758.B768@khan.acc.umu.se>; from tao@acc.umu.se on Sun, Oct 29, 2000 at 11:27:58AM +0100
On Sun, Oct 29, 2000 at 11:27:58AM +0100, David Weinehall wrote:
> On Sat, Oct 28, 2000 at 06:43:42PM -0500, Stephen Crowley wrote:
> > kernel 2.4.0-test10-pre6, but this has been here as long as I can
> > remember.
> >
> > starting wine triggers the bug, C: points to /win2k which is an NTFS
> > filesystem.
>
> Yep, there's a solution for this. Get yourself the complete
> specifications for the Win2K NTFS, and implement it. The kernel NTFS
> simply doesn't support the Win2K NTFS, and rather than risking anything,
> it just OOPS:es. Not that I have any Win2K systems, but if I had, I'd
> damn sure rather see the kernel OOPS than those filesystems trashed.
I see.. but the FS is mounted read-only, so even if it didn't oops why would
there be a risk of it getting trashed? I really wouldn't mind if it did got
trashed.. thanks for the pointer though.
--
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-10-29 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-28 23:43 kernel BUG at fs.c:567 Stephen Crowley
2000-10-29 10:27 ` David Weinehall
2000-10-29 17:25 ` Stephen Crowley [this message]
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=20001029112514.A20492@intolerance.digitalpassage.com \
--to=stephenc@digitalpassage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tao@acc.umu.se \
/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