This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Using thread-specific credentials on Linux in Samba with glibc.
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Jeremy Allison <jra at samba dot org>
- Cc: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, libc-help at sourceware dot org, GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 2 Jul 2012 15:10:53 -0700 (PDT)
- Subject: Re: Using thread-specific credentials on Linux in Samba with glibc.
- References: <20120702161706.GA9979@samba2><CAAHN_R3n3p6RHjGes_-0ehMWAE+YBu7rU9GfjrBtmjfQRJEV7Q@mail.gmail.com><20120702165708.GA10225@samba2><CAAHN_R2NKbV57FzZ9E6pOummb_A0qSx4k0=XPEpaO5YTNVNq2w@mail.gmail.com><20120702214441.GA19241@samba2>
> Just to make things extremely clear, what we're hoping for is
> an acknowlegement from the glibc maintainers that using syscall()
> in this way to get per-process thread credentials on Linux
> platforms is allowed by glibc, in that if it gets accidently
> broken in future by glibc changes (as can happen with any
> software of course :-) then it would be considered a bug.
The context remains utterly muddy and we are not going to read a giant
thread to tease out what you are asking. Show us an example of a use of
the syscall function that you are seeking a clarification on the validity of.