linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Matthew Garrett <mjg@redhat.com>,
	hch@infradead.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] hfsplus: Fix bless ioctl when used with hardlinks
Date: Sun, 17 Jun 2012 17:01:04 -0400	[thread overview]
Message-ID: <20120617210104.GA22818@infradead.org> (raw)
In-Reply-To: <CA+5PVA5EAi7O3nLGdxxJo5Hrp3+NJeBuW_Rtxj0QowpUKeGnYw@mail.gmail.com>

On Wed, Jun 13, 2012 at 07:57:24AM -0400, Josh Boyer wrote:
> On Mon, Apr 16, 2012 at 4:57 PM, Matthew Garrett <mjg@redhat.com> wrote:
> > HFS+ doesn't really implement hard links - instead, hardlinks are indicated
> > by a magic file type which refers to an indirect node in a hidden
> > directory. The spec indicates that stat() should return the inode number
> > of the indirect node, but it turns out that this doesn't satisfy the
> > firmware when it's looking for a bootloader - it wants the catalog ID of
> > the hardlink file instead. Fix up this case.
> >
> > Signed-off-by: Matthew Garrett <mjg@redhat.com>
> > ---
> >
> > V2 cleans up the casting.
> 
> Did this patch get dropped on the floor?  It's been almost 2 months
> since it was submitted.

It just got missed, sorry.  I'll send it along ASAP.

      reply	other threads:[~2012-06-17 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 20:57 [PATCH V2] hfsplus: Fix bless ioctl when used with hardlinks Matthew Garrett
2012-06-13 11:57 ` Josh Boyer
2012-06-17 21:01   ` Christoph Hellwig [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=20120617210104.GA22818@infradead.org \
    --to=hch@infradead.org \
    --cc=jwboyer@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).