On Wed, Dec 16, 2015 at 5:44 PM, Rich Felker <dalias@xxxxxxxx> wrote: > On Wed, Dec 16, 2015 at 05:27:03PM -0500, Zack Weinberg wrote: >> > 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? > > The vdso is library code provided by the kernel, but there's no > fundamental reason to expect it to behave identically to the system > call. Applications making the system call themselves directly will > never end up calling the vdso code, so it doesn't matter if its > behavior in corner cases like this is the same as the syscall. OK. I'm just asking because the segfault happens inside the vDSO, or anyway that's what it looks like from the debugger. (I don't have a problem with keeping everything the way it is behavior-wise, for the record.) zw -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
