From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: geert@linux-m68k.org (Geert Uytterhoeven),
carstenl@mips.com (Carsten Langgaard),
linux-mips@oss.sgi.com
Subject: Re: Filesystem corruption
Date: Mon, 5 Feb 2001 14:01:14 -0800 [thread overview]
Message-ID: <20010205140114.D3880@bacchus.dhis.org> (raw)
In-Reply-To: <E14PlGy-0003IW-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Feb 05, 2001 at 01:01:33PM +0000
On Mon, Feb 05, 2001 at 01:01:33PM +0000, Alan Cox wrote:
> > Is the zero page mapped on non-m68k architectures?
>
> It can certainly be hit by DMA and kernel memory ops
>
> > > I dont believe any 2.4 is currently 'safe'
> > Ugh...
>
> We'll get there, its doing pretty well for most folks
I hope so. For many of us 2.2 is no longer an option. That is at least
without heavy patching to add support for hardware that isn't supported
by 2.2.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Carsten Langgaard <carstenl@mips.com>,
linux-mips@oss.sgi.com
Subject: Re: Filesystem corruption
Date: Mon, 5 Feb 2001 14:01:14 -0800 [thread overview]
Message-ID: <20010205140114.D3880@bacchus.dhis.org> (raw)
Message-ID: <20010205220114.rdpSksdT93RGumCAgRNK2wSnXtp2I3GG_FfzowhoUF0@z> (raw)
In-Reply-To: <E14PlGy-0003IW-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Feb 05, 2001 at 01:01:33PM +0000
On Mon, Feb 05, 2001 at 01:01:33PM +0000, Alan Cox wrote:
> > Is the zero page mapped on non-m68k architectures?
>
> It can certainly be hit by DMA and kernel memory ops
>
> > > I dont believe any 2.4 is currently 'safe'
> > Ugh...
>
> We'll get there, its doing pretty well for most folks
I hope so. For many of us 2.2 is no longer an option. That is at least
without heavy patching to add support for hardware that isn't supported
by 2.2.
Ralf
next prev parent reply other threads:[~2001-02-05 22:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 14:20 Filesystem corruption Carsten Langgaard
2001-01-31 15:52 ` Florian Lohoff
2001-01-31 16:24 ` Carsten Langgaard
2001-01-31 16:48 ` Florian Lohoff
2001-02-05 10:02 ` Ralf Baechle
2001-02-05 12:10 ` Alan Cox
2001-02-05 12:10 ` Alan Cox
2001-02-05 12:56 ` Geert Uytterhoeven
2001-02-05 13:01 ` Alan Cox
2001-02-05 13:01 ` Alan Cox
2001-02-05 22:01 ` Ralf Baechle [this message]
2001-02-05 22:01 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 13:16 Ian Chilton
2001-02-05 16:00 Ian Chilton
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=20010205140114.D3880@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=carstenl@mips.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox