public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
	Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] partitions/msdos.c
Date: Sun, 27 Feb 2005 00:40:53 +0100	[thread overview]
Message-ID: <20050226234053.GA14236@apps.cwi.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0502261510030.25732@ppc970.osdl.org>

On Sat, Feb 26, 2005 at 03:12:28PM -0800, Linus Torvalds wrote:

> > The default fdisk will assign type 83 to a newly created partition.
> 
> Ok. Is that a "it has done so for the last 5 years" thing? 

The last twelve years.

> > (About type 0: DOS has used type 0 as definition of unused. It is not
> > bad if Linux uses DOS-conventions for a DOS-type partition table.)
> 
> Agreed. At the same time, I could well imagine that some people might use 
> such a type exactly to make DOS ignore it (but I assume the same is true 
> of the regular 0x83 type too, so maybe I'm just being difficult).
> 
> There's certainly a good argument for fixing a known problem (Uwe) and a 
> small enough risk of it breaking anything else.

Yes.

Andries


(Concerning the "size" version: it occurred to me that there is one
very minor objection: For extended partitions so far the size did
not normally play a role. Only the starting sector was significant.
If, at some moment we decide also to check the size, then a weaker
check, namely only checking for non-extended partitions, might be
better at first.)

(Yes, disk capacity is not always known - see e.g. ll_rw_blk.c:
 /* Test device or partition size, when known. */
See also sd.c, with the strange
                sdkp->capacity = 0x200000; /* 1 GB - random */
In such cases we just access the blocks user space tells us to access.)

  reply	other threads:[~2005-02-26 23:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 21:35 [PATCH] partitions/msdos.c Andries Brouwer
2005-02-26 22:04 ` Uwe Bonnes
2005-02-26 22:28   ` Linus Torvalds
2005-02-26 22:35     ` Linus Torvalds
2005-02-26 23:24       ` Uwe Bonnes
2005-02-26 23:46         ` Linus Torvalds
2005-02-26 23:53           ` Andries Brouwer
2005-02-26 22:52     ` Andries Brouwer
2005-02-26 23:12       ` Linus Torvalds
2005-02-26 23:40         ` Andries Brouwer [this message]
2005-02-26 23:49           ` Linus Torvalds
2005-02-27  0:47             ` Uwe Bonnes
2005-02-27  1:04               ` Linus Torvalds
2005-02-27 14:33                 ` Uwe Bonnes
2005-02-27  1:07               ` Andries Brouwer
2005-03-01  6:53           ` Rogier Wolff
2005-03-19 21:54 ` Werner Almesberger
2005-03-19 22:28   ` Grzegorz Kulewski

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=20050226234053.GA14236@apps.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=akpm@osdl.org \
    --cc=bon@elektron.ikp.physik.tu-darmstadt.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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