public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Florian Weimer <fweimer@redhat.com>,
	Rical Jasan <ricaljasan@pacific.net>
Cc: libc-alpha <libc-alpha@sourceware.org>,
	Carlos O'Donell <carlos@redhat.com>
Subject: Re: [RFC] DT_WHT
Date: Mon, 05 Mar 2018 16:21:00 -0000	[thread overview]
Message-ID: <1520266855.2786.75.camel@codethink.co.uk> (raw)
In-Reply-To: <ee5a5820-cd01-03f8-4085-13ef81d97a96@redhat.com>

On Mon, 2018-03-05 at 10:47 +0100, Florian Weimer wrote:
> On 03/05/2018 02:50 AM, Ben Hutchings wrote:
> > I have no opinion on that code, but it sounded like you proposed to
> > remove the macro definition too.  I wanted to point out that the macro
> > is meaningful and may be useful to applications.
> 
> Useful in what sense?  What are its semantics?

A white-out entry is a placeholder written to the upper layer of a
union filesystem that hides an entry in the lower layer.

You'll never see these directory entries when looking at the union
filesystem, but can do if you look at the upper layer directly.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2018-03-05 16:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 10:49 Rical Jasan
2018-02-22  7:03 ` Carlos O'Donell
2018-03-01 16:24 ` Ben Hutchings
2018-03-01 23:02   ` Rical Jasan
2018-03-05  1:50     ` Ben Hutchings
2018-03-05  9:47       ` Florian Weimer
2018-03-05 16:21         ` Ben Hutchings [this message]
2018-03-06 11:28           ` Florian Weimer
2018-03-05 10:49       ` Rical Jasan
2018-03-05 16:23         ` Ben Hutchings

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=1520266855.2786.75.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=ricaljasan@pacific.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).