bug(mknod): when using --context in Non Selinux kernel, it does not warn
Open
Nobody has claimed this yet.
U - mknod
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Hi, uutils mainteners
as i confirmed that the uu mknod do not output the warning while the gnu one does, as our test confirmed
relunsec@relunsec:~/software/coreutils/target/debug$ sudo gnumknod --context=con g block 1 1
[sudo: authenticate] Password:
gnumknod: warning: ignoring --context; it requires an SELinux/SMACK-enabled kernel
relunsec@relunsec:~/software/coreutils/target/debug$ sudo ./mknod --context=con u block 1 1
relunsec@relunsec:~/software/coreutils/target/debug$
Contributor 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.
Research direction
Start by locating the Rust mknod entry point and its existing --context handling, then run the issue's command on a non-SELinux kernel and inspect the relevant mknod tests. Done means the command emits the GNU-compatible warning when --context is ignored, with behavior on supported kernels still covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100