mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, prw@ceiriog1.demon.co.uk
Subject: Re: [2.6-git PATCH] Fix for HFSPlus, should go in before 2.6.14!
Date: Wed, 26 Oct 2005 10:33:31 +0100	[thread overview]
Message-ID: <1130319211.8284.18.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0510261053300.1386@scrub.home>

Hi,

On Wed, 2005-10-26 at 10:59 +0200, Roman Zippel wrote:
> On Wed, 26 Oct 2005, Anton Altaparmakov wrote:
> 
> > Please apply before you release 2.6.14 if at all possible as HFS+ is 
> > seriously borked without it...  I have now given up waiting for Roman to 
> > reply given my original mail to him was two weeks ago and you are about 
> > to release 2.6.14...
> 
> I haven't responded yet, because I didn't have the time to verify and test 
> the problem yet. It's not "seriously borked", it doesn't crash, it still 
> works and the problem is easily fixed by fsck, so it wasn't on the top of 
> my todo list.

That is fair enough.  It is high on my TODO list so I sent the patch
bypassing you (and you were still CC:-ed so you could object if you
wanted).

I didn't even know there is an fsck for HFS+ (the one in hfsplusutils is
read-only so not much use - now I have found out pdisk contains it but
pdisk is not found on i386 distributions, at least not on SUSE 9.3 which
I was using at the time).

Nowhere in the kernel documentation (not in the Kconfig and not in
Documentation/filesystems anyway) is there anything about hfsplus.
There is a mention of hfsutils but not hfsplusutils or pdisk...  Perhaps
a documentation update is on order?

For me this bug meant I could no longer copy files to the disk and
wasted a day that way as it was full even though I deleted files to make
space and I had to take it back home to fix things on OSX and take it
back to work the next day to copy the files on Linux...

Anyway, requiring an fsck after every umount definitely fits my
definition of seriously borked.  YMMV.  (-:

> The patch looks fine, although I'd probably prefered to move this kind of 
> initialization into a separate function, as it's duplicated right now.

What is stopping you from doing so at some later point in time?

Whenever my git pull shows me that patches have hit fs/ntfs/ I look at
them and change them if I don't like something and make a new commit.
Andrew pulls my git repository for each -mm so it gets in that way to
-mm and I submit regular-ish updates to Linus for inclusion so for small
things like that they just get queued until a bigger submit.  Anyway,
that's just how I work.  (-:

Best regards,

        Anton
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/


      reply	other threads:[~2005-10-26  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26  7:30 Anton Altaparmakov
2005-10-26  8:59 ` Roman Zippel
2005-10-26  9:33   ` Anton Altaparmakov [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=1130319211.8284.18.camel@imp.csi.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prw@ceiriog1.demon.co.uk \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®