mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Randy Dunlap <rddunlap@osdl.org>,
	fastboot@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: kexec and IRQ sharing
Date: Mon, 7 Mar 2005 14:24:18 -0800	[thread overview]
Message-ID: <200503071424.18645.david-b@pacbell.net> (raw)
In-Reply-To: <m1k6ojm7n2.fsf@ebiederm.dsl.xmission.com>

On Monday 07 March 2005 2:08 pm, Eric W. Biederman wrote:

> 
> The ongoing DMA transfers which are companions of the irq generating
> events are what really concern me, as we could get all kinds of
> interesting memory stomps.  Do you think you could implement
> a reboot notifier or a shutdown() method to handle that case?
> 
> This appears to be yet another case of kexec transforming theoretical
> bugs into actual ones.  Groan.

Reboot notifiers seem to be a more general solution than the
driver model shutdown() hooks, since as Alan noted not every
bus framework uses shutdown() ... and although remove() would
solve the issue too, for essentially all busses, it doesn't
kick in here (and linker tricks may have removed it anyway).

Of possible relevance:  Documentation/arm/Booting lists, at
the end, requirements the boot firmware must meet before it
runs Linux.  (Stuff like U-Boot, BLOB, HaRET, or dozens of
other open-sourced analogues of x86 BIOS code.)  Seems like
the same rules will apply before kexec ... yes?  That mentions
DMA, though not IRQs (possibly an omission).

- Dave


      reply	other threads:[~2005-03-07 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.0503071555530.1789-100000@ida.rowland.org>
2005-03-07 22:08 ` Eric W. Biederman
2005-03-07 22:24   ` David Brownell [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=200503071424.18645.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rddunlap@osdl.org \
    --cc=stern@rowland.harvard.edu \
    /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

all inboxes | Powered by JetHome®