public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andi Kleen <andi@firstfloor.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: agpgart: when telling user you'll corrupt his data, at least do it at KERN_CRIT
Date: Fri, 28 Mar 2008 15:13:48 +0100	[thread overview]
Message-ID: <20080328141348.GE29218@elte.hu> (raw)
In-Reply-To: <20080328134451.GB4544@ucw.cz>


* Pavel Machek <pavel@ucw.cz> wrote:

> On Fri 2008-03-28 12:35:28, Ingo Molnar wrote:
> > 
> > * Pavel Machek <pavel@ucw.cz> wrote:
> > 
> > > IOMMU off means very bad stuff may happen, like data corruption on 
> > > your hard drives. At least tells users this is serious...
> > 
> > ouch. Please at minimum lets turn this into a panic(), but best would be 
> > to trim memory in this case, hm?
> 
> Andi tells me we already fallback to swiotlb, so messages are not on 
> wrong loglevel; they contain confusing/obsolete text.

yes that is the theory - but how did your disk get corrupted in 
practice? ;-)

	Ingo

  reply	other threads:[~2008-03-28 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 11:25 agpgart: when telling user you'll corrupt his data, at least do it at KERN_CRIT Pavel Machek
2008-03-28 11:35 ` Andi Kleen
2008-04-01 12:24   ` agpgart: scary messages are fortunately obsolete Pavel Machek
2008-04-01 13:33     ` Andi Kleen
2008-04-04  8:55     ` Ingo Molnar
2008-03-28 11:35 ` agpgart: when telling user you'll corrupt his data, at least do it at KERN_CRIT Ingo Molnar
2008-03-28 12:48   ` Jiri Kosina
2008-03-28 12:51     ` Ingo Molnar
2008-03-28 13:44   ` Pavel Machek
2008-03-28 14:13     ` Ingo Molnar [this message]
2008-03-28 14:25       ` Andi Kleen
2008-04-01 12:13       ` Pavel Machek

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=20080328141348.GE29218@elte.hu \
    --to=mingo@elte.hu \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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