All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Larger dev_t and major/minor split
Date: Thu, 20 Mar 2003 16:02:06 -0800	[thread overview]
Message-ID: <3E7A567E.3080409@zytor.com> (raw)
In-Reply-To: <20030320234946.GT2835@ca-server1.us.oracle.com>

Joel Becker wrote:
> On Thu, Mar 20, 2003 at 03:06:31PM -0800, H. Peter Anvin wrote:
> 
>>Last I checked, all traditional (inode-based) Unix filesystems,
>>including ext2/3 used block pointers for dev_t.  There are plenty of
>>block pointers; 60 bytes worth.
> 
> 	They do indeed.  But ext2/3 touches that block pointer with
> cpu_to_le32() and friends.  It needs fixing at best, and compatability
> work for already existing partitions.
> 

A few options:

a) Use an inode flag indicating a large dev_t.  This is probably the
best option.

b) Use a sentinel value, e.g. 0xffffffff, to indicate that the major and
minor are in block pointers 1 and 2.

	-hpa



  reply	other threads:[~2003-03-20 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 21:42 Larger dev_t and major/minor split H. Peter Anvin
2003-03-20 22:09 ` Joel Becker
2003-03-20 23:06   ` H. Peter Anvin
2003-03-20 23:49     ` Joel Becker
2003-03-21  0:02       ` H. Peter Anvin [this message]
2003-03-20 22:47 ` Greg KH

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=3E7A567E.3080409@zytor.com \
    --to=hpa@zytor.com \
    --cc=Joel.Becker@oracle.com \
    --cc=linux-kernel@vger.kernel.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 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.