From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Anders Gustafsson <andersg@0x63.nu>,
arjanv@redhat.com, linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: [PATCH] devexit fixes in i82092.c
Date: 16 Mar 2002 12:27:21 -0700 [thread overview]
Message-ID: <m1lmcsxqhy.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0203151659060.1379-100000@home.transmeta.com> <3C92AD1F.30909@mandrakesoft.com>
In-Reply-To: <3C92AD1F.30909@mandrakesoft.com>
Jeff Garzik <jgarzik@mandrakesoft.com> writes:
>
> (thinking vaguely long-term)
>
> I wonder if mochel already code for this, or has thought about this... Just like
>
> suspend, IMO we ideally should use the device tree to shutdown the system,
> agreed?
>
> Further, I wonder if the reboot/shutdown notifiers can be replaced with device
> tree control over those events...
Please for the Linux booting Linux scenario it is mandatory we get this right
for reboot. I know for a fact that currently we leave active receive buffers on
network cards when we reboot. (If you haven't downed the interface). So it
is possible for a network packet to come in and hose a machine that is rebooting.
Occasionally I test my linux booting linux code by loading memtest86 to make certain
I don't have something like that going on. And the first time I tried it I hadn't
downed the interfaces and I actually saw a network packet come in and corrupt
memory. I also have similar reports from other about disk subsystems.
Eric
next prev parent reply other threads:[~2002-03-16 19:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 0:57 [PATCH] devexit fixes in i82092.c Anders Gustafsson
2002-03-16 1:00 ` Linus Torvalds
2002-03-16 2:25 ` Jeff Garzik
2002-03-16 7:40 ` Linus Torvalds
2002-03-16 7:51 ` Keith Owens
2002-03-16 8:13 ` Linus Torvalds
2002-03-16 9:00 ` Jeff Garzik
2002-03-16 9:50 ` Keith Owens
2002-03-25 19:15 ` Patrick Mochel
2002-03-16 8:51 ` Jeff Garzik
2002-03-16 17:35 ` Alan Cox
2002-03-16 17:31 ` Jeff Garzik
2002-03-25 19:19 ` Patrick Mochel
2002-03-16 9:40 ` Arjan van de Ven
2002-03-22 15:47 ` Pavel Machek
2002-03-16 10:32 ` David Woodhouse
2002-03-16 19:27 ` Eric W. Biederman [this message]
2002-03-16 21:00 ` Alan Cox
2002-03-16 22:03 ` Eric W. Biederman
2002-03-16 22:28 ` Alan Cox
2002-03-16 22:16 ` Eric W. Biederman
2002-03-16 22:26 ` Linus Torvalds
2002-03-16 23:00 ` Eric W. Biederman
2002-03-16 23:15 ` Dave Jones
2002-03-21 15:12 ` Pavel Machek
2002-03-25 19:02 ` Patrick Mochel
-- strict thread matches above, loose matches on Subject: below --
2002-03-24 23:36 Alexander Stohr
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=m1lmcsxqhy.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=andersg@0x63.nu \
--cc=arjanv@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.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