From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH,TRIVIAL] AF_UNIX, accept() and addrlen
Date: Mon, 24 Mar 2008 12:17:19 +0000 [thread overview]
Message-ID: <20080324121719.GJ4434@implementation.uk.xensource.com> (raw)
In-Reply-To: <87abko734d.fsf@basil.nowhere.org>
Andi Kleen, le Mon 24 Mar 2008 12:50:10 +0100, a écrit :
> Samuel Thibault <samuel.thibault@ens-lyon.org> writes:
>
> > David Miller, le Sun 23 Mar 2008 21:56:41 -0700, a écrit :
> > > From: Samuel Thibault <samuel.thibault@ens-lyon.org>
> > > Date: Sat, 8 Mar 2008 02:23:21 +0000
> > >
> > > > Accept and getpeername are supposed to return the amount of bytes
> > > > written in the returned address. However, on unnamed sockets, only
> > > > sizeof(short) is returned, while a 0 is put in the sun_path member.
> > > > This patch adds 1 for that additional byte.
> > > >
> > > > Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> > >
> > > This change isn't correct. It's the fact that the
> > > length returned is sizeof(short) that tells the caller
> > > that the unix socket is unnamed.
> >
> > Mmm, where that is documented?
> >
> > I can't find any details about that in SUS, and man 7 unix says
> >
> > `If sun_path starts with a null byte ('' '), then it refers to the
> > abstract namespace main- tained by the Unix protocol module.'
>
> [I wrote unix(7) originally]. The abstract name space is a Linux
> extension and there is no written standard and whatever the kernel
> implements is the de-facto standard. If unix(7) differs in anything
> from what the code does please send patches to the manpages
> maintainer.
Oops, sorry, we are not talking about abstract namespace actually (their
sockaddr length are necessarily bigger than sizeof(sa_family_t) since
they need some data), but unamed sockets. So the Address Format
paragraph just misses description of unnamed sockets.
Samuel
next prev parent reply other threads:[~2008-03-24 12:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 2:23 [PATCH,TRIVIAL] AF_UNIX, accept() and addrlen Samuel Thibault
2008-03-24 4:56 ` David Miller
2008-03-24 10:43 ` Samuel Thibault
2008-03-24 11:50 ` Andi Kleen
2008-03-24 12:17 ` Samuel Thibault [this message]
2008-03-24 12:27 ` Samuel Thibault
2008-03-31 4:00 ` Michael Kerrisk
2008-03-31 9:44 ` Samuel Thibault
2008-03-31 18:51 ` Michael Kerrisk
2008-04-18 16:52 ` Michael Kerrisk
2008-04-24 0:16 ` Samuel Thibault
2008-04-24 8:31 ` Michael Kerrisk
2008-04-26 1:44 ` Samuel Thibault
2008-04-27 5:54 ` David Miller
2008-05-12 13:10 ` Michael Kerrisk
2008-05-12 13:20 ` Samuel Thibault
2008-03-24 20:23 ` David Miller
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=20080324121719.GJ4434@implementation.uk.xensource.com \
--to=samuel.thibault@ens-lyon.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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.