All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Alexander Viro
	<viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
	Andreas Gruenbacher
	<a.gruenbacher-bdq14YP6qtRg9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH 1/1] listxattr.2: provide example code
Date: Mon, 09 Feb 2015 10:22:49 +0100	[thread overview]
Message-ID: <54D87C69.6040008@gmail.com> (raw)
In-Reply-To: <trinity-8f8ea4c5-76d3-462f-8ec4-c6ead7c3f6d4-1423473495556@msvc245>

Hi Heinrich

On 02/09/2015 10:18 AM, Heinrich Schuchardt wrote:
> Hello Michael,
> 
> listxattr is implemented individually by the different filesystems.
> 
> Tmpfs delivered a double zero in my tests. The length included this double zero.
> 
> I need to check the coding of all file systems. They might be different.

Oh -- was unaware of that oddity of tmpfs! That sounds like a bug to me.
All of the traditional filesystems don't return doubled null at the end
of the buffer, AFAIK.

Cheers,

Michael


--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-02-09  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 16:22 [PATCH 1/1] listxattr.2: provide example code Heinrich Schuchardt
     [not found] ` <1423412528-11512-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2015-02-09  8:42   ` Michael Kerrisk (man-pages)
     [not found]     ` <54D872EE.8070000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-09  9:18       ` Heinrich Schuchardt
2015-02-09  9:22         ` Michael Kerrisk (man-pages) [this message]
2015-02-09  9:42         ` Michael Kerrisk (man-pages)

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=54D87C69.6040008@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=a.gruenbacher-bdq14YP6qtRg9hUCZPvPmw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
    --cc=xypron.glpk-Mmb7MZpHnFY@public.gmane.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.