From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215514] New: Documentation: meaning of device number / ID in `stat` and `stat()`
Date: Fri, 21 Jan 2022 12:40:08 +0000 [thread overview]
Message-ID: <bug-215514-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215514
Bug ID: 215514
Summary: Documentation: meaning of device number / ID in `stat`
and `stat()`
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: jwagner@computing.dcu.ie
Regression: No
The man page `man 2 stat` for `stat()` gives the impression that `stat.st_dev`
is always composed of major and minor of an existing block device. However,
filesystems such as `btrfs` allocate new device number not (clearly) related to
the underlying device(s). The description of `st_dev` needs to be updated.
Similarly, a clarification would be useful in `man 1 stat` either directly in
the description of the `%d` and `%D` formats or after the formats table.
My system: openSUSE Leap 15.3
Checked in current man pages as of 2022-01-21:
* https://man7.org/linux/man-pages/man2/stat.2.html
* https://man7.org/linux/man-pages/man1/stat.1.html
Related:
* https://github.com/util-linux/util-linux/issues/1562 (closed, wrong place)
Breadcrumbs:
* https://github.com/util-linux/util-linux/issues/1563 (closed, wrong place)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2022-01-21 12:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-215514-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox