Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
As you can see and it is also documented, "mknod-b", "mknod-c", and "mkfifo" are just wrappers to "mknod", just adding the bit for the node type (block device, character device, fifo).
If they are used correctly, i.e. just passing permissions as mode, they behave as described, so I don't consider this a big issue.
In any case, patch posted:
https://www.redhat.com/archives/libguestfs/2015-January/msg00040.html
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2183.html
Description of problem: The way libguestfs handle "mode" in "mknod-b" "mknod-c" "mkfifo" have some bugs. The source code are: int do_mkfifo (int mode, const char *path) { return do_mknod (mode | S_IFIFO, 0, 0, path); } int do_mknod_b (int mode, int devmajor, int devminor, const char *path) { return do_mknod (mode | S_IFBLK, devmajor, devminor, path); } int do_mknod_c (int mode, int devmajor, int devminor, const char *path) { return do_mknod (mode | S_IFCHR, devmajor, devminor, path); } /usr/include/bits/stat.h #define __S_IFCHR 0020000 /* Character device. */ #define __S_IFBLK 0060000 /* Block device. */ #define __S_IFIFO 0010000 /* FIFO. */ "mknod-c 0060XXX" == "mknod 0060XXX", In this case, "mknod-c" will create a block device. "mkfifo 0000XXX" == "mkfifo 0010XXX", In this case, returning an error would be better. Version-Release number of selected component (if applicable): libguestfs-tools-c-1.28.1-1.17.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. create a img, and add the img # guestfish -N fs:ext3 2. use mknod, mknod-b, mknod-c to create device ><fs> mknod-c 0060777 8 1 /test_mknod_c ><fs> mkfifo 0000777 /test_mkfifo ><fs> ll / total 17 drwxr-xr-x 3 root root 1024 Jan 15 04:29 . drwxr-xr-x 19 root root 4096 Jan 15 03:40 .. drwx------ 2 root root 12288 Jan 15 03:41 lost+found prwxr-xr-x 1 root root 0 Jan 15 04:29 test_mkfifo brwxr-xr-x 1 root root 8, 1 Jan 15 04:28 test_mknod_c Actual results: mknod-c create a block device, and mkfifo create a fifo device when given a wrong mode. Expected results: If the mode doesn't match the device mode, libguestfs returns an "Invalid argument" error. Additional info: ...