On 2022-12-04 10:07, Luke Dashjr wrote:
Version: sys-apps/coreutils-9.1-r1 (Gentoo)
Context: Linux has a long-standing bug which leads to ext4 RAM dishs (zram
specifically) getting corrupted randomly. This manifests as various
newfstatat calls returning -1 errno=EUCLEAN (Structure needs cleaning
On Tuesday 06 December 2022 19:08:57 Paul Eggert wrote:
> On 2022-12-04 10:07, Luke Dashjr wrote:
> > Version: sys-apps/coreutils-9.1-r1 (Gentoo)
> >
> > Context: Linux has a long-standing bug which leads to ext4 RAM dishs
> > (zram specifically) getting corrupted randomly. This manifests as variou
I don't see any failures in stat-like syscalls there, so it looks like
at least the bug you mentioned has mutated (even if it hasn't been
fixed...).
Who's calling 'abort' and why? You can use GDB to find out.
On Wednesday 07 December 2022 00:35:17 Paul Eggert wrote:
> Who's calling 'abort' and why? You can use GDB to find out.
That was the stack trace in the original report ;)
Here's a `bt full`:
#0 0x77dab80c in __pthread_kill_implementation (threadid=, signo=, no_tid=no_tid@entry=0) at pth
On 12/6/22 17:02, Luke Dashjr wrote:
That was the stack trace in the original report ;)
OK.
newfstatat(4, "banlist.json", {st_mode=S_IFDIR|0700, st_size=4096, ...},
AT_SYMLINK_NOFOLLOW) = 0
openat(4, "banlist.json",
O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW|O_CLOEXEC|O_DIRECTORY) = 3
newfstat
On Wednesday 07 December 2022 01:59:27 Paul Eggert wrote:
> On 12/6/22 17:02, Luke Dashjr wrote:
> > newfstatat(4, "banlist.json", {st_mode=S_IFDIR|0700, st_size=4096, ...},
> > AT_SYMLINK_NOFOLLOW) = 0 openat(4, "banlist.json",
> > O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW|O_CLOEXEC|O_DIRECTORY) = 3
