Hi,
On 2022-03-29 17:53, Joshua Hudson wrote:
> diff -ur glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c
> glibc/glibc/sysdeps/unix/sysv/linux/pathconf.c
> --- glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c2022-03-29
> 17:50:12.558027042 -0700
> +++ glibc/glibc/sysdeps/unix/sysv/linux
diff -ur glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c
glibc/glibc/sysdeps/unix/sysv/linux/pathconf.c
--- glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c2022-03-29
17:50:12.558027042 -0700
+++ glibc/glibc/sysdeps/unix/sysv/linux/pathconf.c2022-03-29
17:52:33.262157543 -0700
@@ -18
/* reproduce glibc bug */
/*
* I don't typically care what the return of pathconf(..., _PC_LINK_MAX)
* is; I just care whether or not it's greater than 1 because I'm checking
* whether the filesystem supports hard links or not.
*/
#include
#include
#include
#include
#include
#include
i
Package: libc6
Version: All of them
Severity: normal
Tags: newcomer
Dear Maintainer,
what lead up to the situation is well-described in my stackoverflow post:
https://stackoverflow.com/questions/71641957/how-to-check-if-a-filesystem-supports-hard-links-in-linux
Since posting it, I have traced th
4 matches
Mail list logo