Red Hat Bugzilla – Bug 582929
mknod doesn't check for invalid mode
Last modified: 2010-05-20 20:31:20 EDT
Description of problem:
When create device file via mknod with invalid mode, it just succeeds but not reports any error. This is quite like the situation in BZ #582901.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ><fs> mknod-b 066666 8 1 /sd
mknod_b 28086 8 1 "/sd"
send_to_daemon: 0x25eb050 g->state = 3, n = 48
recv_from_daemon: 0x25eb050 g->state = 3, size_rtn = 0x7fffdb87b84c, buf_rtn = 0x7fffdb87b840
proc 135 (mknod_b) took 0.03 seconds
2. ><fs> ll /sd
send_to_daemon: 0x25eb050 g->state = 3, n = 36
recv_from_daemon: 0x25eb050 g->state = 3, size_rtn = 0x7fffdb87b86c, buf_rtn = 0x7fffdb87b860
ls -la /sysroot/sd
proc 5 (ll) took 0.00 seconds
brwSr-Sr-- 1 root root 8, 1 Apr 16 07:45 /sysroot/sd
When you use a invalid mode, mknod should exit and report error.
libguestfs-1.2.3-1.el5 has been submitted as an update for Fedora EPEL 5.
libguestfs-1.2.3-1.fc13 has been submitted as an update for Fedora 13.
libguestfs-1.2.3-1.fc12.6 has been submitted as an update for Fedora 12.
libguestfs-1.2.3-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.