All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrey Borzenkov <arvidjaar@newmail.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Ghost EDD devices in /sys again
Date: Sun, 28 Sep 2008 08:12:26 -0700	[thread overview]
Message-ID: <48DF9EDA.1060809@zytor.com> (raw)
In-Reply-To: <200809281035.06547.arvidjaar@newmail.ru>

Andrey Borzenkov wrote:
> On Sunday 07 September 2008, H. Peter Anvin wrote:
>> I think this is closer to what we really want; after all, memory being written is the "first principles" test that applies here.
>>
> 
> OK I have been using this for some time. I do not actually insist on
> returning "failure" for zero signature; my main concern was duplicated
> signature resulted from not clearing read buffer. Still I assume that
> zero signature is the same as no signature; i.e. even if disk is physically
> present but zeroed out there is no point in presenting mbr_signature in
> sysfs either.
> 

Right, I think that's a much better patch.

The really Right Thing[TM] to do is probably to pre-clear the buffer and 
then look for the 0xaa55 signature at offset 510; it is required for 
sector 0 to be a valid MBR-format partition table and hence for the MBR 
*signature* to be valid.

I'll write that up tomorrow (I'm travelling today), or you can send me a 
patch.

	-hpa


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 22:08 [PATCH] Ghost EDD devices in /sys again H. Peter Anvin
2008-09-28  6:34 ` Andrey Borzenkov
2008-09-28 15:12   ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-05 18:19 Andrey Borzenkov
2008-09-06  8:40 ` [PATCH] " Andrey Borzenkov
2008-09-06 12:07   ` Ingo Molnar
2008-09-06 14:34     ` Ingo Molnar
2008-09-06 14:04   ` H. Peter Anvin
2008-09-06 17:46     ` Andrey Borzenkov

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=48DF9EDA.1060809@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=arvidjaar@newmail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.