ls: --colors=always -l . calls llistxattr twice for the same file
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 35/100
Research direction
The payload names only the ls command run with --color=always -l . and the llistxattr system calls seen in the strace output, so start by reproducing that trace against a build of this repository's ls. Find where the extended-attribute listing is requested for each entry and why it runs twice when color output is enabled. Linked pull request #15210 is already open against this issue, so read it first and coordinate before starting a parallel fix. Done means one llistxattr call per file in the same strace run.
Written by the indexing model from the issue text.
Description
> ls
file file2
$ strace --trace=llistxattr ls --color=always -l .>/dev/null
llistxattr("./file", "", 4096) = 0
llistxattr("./file2", "", 4096) = 0
llistxattr("./file", "", 4096) = 0
llistxattr("./file2", "", 4096) = 0
+++ exited with 0 +++
$ strace --trace=llistxattr '/home/a/bin/gnu9.12/ls' --color=always -l .>/dev/null
llistxattr(".", "", 152) = 0
llistxattr("file2", "", 152) = 0
llistxattr("file", "", 152) = 0
+++ exited with 0 +++
- Dominant language
- Rust
- Stars
- 24.3k
- Forks
- 2.1k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 327
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uutils/coreutils
-
tac: --separator rejects a value that starts with '-'Possibly taken @emirmrkaljevic claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
minorbug(mv): invalid mode errors not quotedPossibly taken @henrimarconni claimed this 3 days ago. OpenU - mv
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ptx: break file missing path in error messagePossibly taken @Franklin-Qi claimed this 3 days ago. OpenU - ptx
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uutils/coreutils#15307 · 1 comment ·
Maintainers usually reply within 1 day
-
minorbug(stat): os errno not stripped when failing to flush stdoutPossibly taken @cestercian claimed this 10 days ago. OpenU - stat
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
uutils/coreutils#15200 · 3 comments ·
Maintainers usually reply within 1 day
-
stty: support B460800 and B921600 baud ratesPossibly taken @oech3 claimed this 6 days ago. Openawaiting upstream U - stty
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
area:io needs-info needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
bherbruck/solvecraft#3216 · 1 comment ·
-
bug triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
praxis-proxy/grid#412 ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
storytold/photocraft#7824 · 1 comment ·
Maintainers usually reply within 1 day
-
area:ui chore could help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day