The time(2) man page conflicts with glibc

[Zack Weinberg]

On Wed, Dec 16, 2015 at 4:59 PM, Rich Felker <dalias@libc.org> wrote:
>> > Programs could also be calling the syscall directly (using syscall()
>> > or asm) and using it as a (very cheap, fail-safe) way to verify that
>> > an address is writable before attempting to write to it. Breaking this
>> > would be a kernel API regression. However the library function time()
>> > has UB for invalid pointers and no obligation to support them.
>>
>> sure, but that still doesn't mean the kernel should be sending SEGV.
>> which is what this subthread was about.
>
> The kernel is not causing SIGSEGV as far as I can tell; it's purely
> the library function time that's causing this.

... Do you consider the vDSO to be part of the kernel, or part of the C library?