public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH,RFC] umsdos FS in 2.6.x
Date: Fri, 24 Oct 2003 10:16:39 +0100	[thread overview]
Message-ID: <20031024091639.GS7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20031023235327.3ff12194.rddunlap@osdl.org>

On Thu, Oct 23, 2003 at 11:53:27PM -0700, Randy.Dunlap wrote:
> 
> This patch enables umsdos filesystem to build, although a few things
> still need to be fixed, such as:
> 
> . updating {acm}time, since those fields changed from time_t to
>   struct timespec:  for backward compatibility, do these fields
>   need to remain as time_t (i.e., keep the same size) ?
> 
> . I kept using a 16-bit dev_t.  Does this need to change?
>   If yes, to 32-bit, or to use whatever size is passed to it?
> 
> . fill_super/read_super probably still need a little bit of work,
>   such as which inode_operations structure to use.
> 
> . I'll begin testing it soon.

* struct inode reuse between msdos and umsdos is FUBAR.  Allocation/freeing
  of inode is controlled by its ->i_sb.  So is location of struct inode within
  the allocated object.  That's where umsdos got really broken and AFAICS the
  only more or less sane way to handle that crap is separation of msdos and
  umsdos inode/dentry/superblock, so that the latter would refer the former.

The rest is more or less trivial; compile fixes, mostly from prototype changes
for methods.  Inode reuse problem is where the real PITA is and it will take
a serious work to fix.

      reply	other threads:[~2003-10-24  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24  6:53 [PATCH,RFC] umsdos FS in 2.6.x Randy.Dunlap
2003-10-24  9:16 ` viro [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=20031024091639.GS7665@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@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