[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox-cvs
Subject: [Bug 15211] New: Segmentation fault in ls -l
From: bugzilla () busybox ! net
Date: 2022-12-25 13:42:49
Message-ID: bug-15211-161 () https ! bugs ! busybox ! net/
[Download RAW message or body]
https://bugs.busybox.net/show_bug.cgi?id=15211
Bug ID: 15211
Summary: Segmentation fault in ls -l
Product: Busybox
Version: 1.35.x
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Standard Compliance
Assignee: unassigned@busybox.net
Reporter: ja@sdomi.pl
CC: busybox-cvs@busybox.net
Target Milestone: ---
In case of an abnormally high date stored on the fs, busybox's ls -la crashes
on trying to display it. I have experienced this when interfacing with an NTFS3
filesystem which has invalid dates stored in some of the file metadata.
```
(gdb) r -la
Starting program: /bin/ls -la
total 2102692
drwxrwxrwx 1 root root 5804032 Dec 25 12:57 .
drwxr-xr-x 6 root root 4096 Dec 25 11:17 ..
-rwxr-xr-x 1 root root 0 Dec 25 00:39 AUTOEXEC.BAT
-rwxr-xr-x 1 root root 0 Dec 25 00:39 CONFIG.SYS
-r-xr-xr-x 1 root root 0 Dec 25 00:39 IO.SYS
-rw-r--r-- 1 domi domi 523500 Dec 25 13:31 LegacyUpdate-1.3.exe
Program received signal SIGSEGV, Segmentation fault.
__asctime_r (tm=0x7ffff7ffd4c0 <tm>, buf=0x7ffff7ffdd40 <buf> "Wed May 8
04:52:15 23697") at src/time/asctime_r.c:23
23 src/time/asctime_r.c: No such file or directory.
(gdb) bt
#0 __asctime_r (tm=0x7ffff7ffd4c0 <tm>,
buf=0x7ffff7ffdd40 <buf> "Wed May 8 04:52:15 23697")
at src/time/asctime_r.c:23
#1 0x00005555555d12c1 in ?? ()
#2 0x00007fffffffe898 in ?? ()
#3 0x0000000000000000 in ?? ()
(gdb)
```
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
busybox-cvs mailing list
busybox-cvs@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox-cvs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic