* 'clock' of https://github.com/t-8ch/util-linux:
lsclocks: new util to interact with system clocks
lib/timeutils: implement timespec formatting
lib/timeutils: implement nanosecond formatting
lib/timeutils: constify some arguments
utmpdump: validate subsecond granularity
* 'lsfd--xmode' of https://github.com/masatake/util-linux:
lsfd: add 'D' flag for representing deleted files to XMODE column
lsfd: introduce XMODE column, extensible variant of MODE
test: (lsfd) add a subcase for testing NAME column for a deleted file
test: (lsfd) add a case for testing DELETED column
test: (mkfds) add "make-regular-file" factory
* 'lsfd--misc-tun' of https://github.com/masatake/util-linux:
tests: (lsfd) add a case testing TUN.IFACE column
tests: (mkfds) add a factor for opening tun device
lsfd: add TUN.IFFACE, a column for interfaces behind tun devices
lsfd: (refactor) move miscdev specific code to cdev_misc_ops
lsfd: (refactor) make the way to handle character devices extensible
lsfd: (refactor) introduce a content data type for char devices
Usecases:
* Compare current monotonic time to timestamps reported by systemd
* Validate time namespace operations
* Inspect clock resolutions
Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
The implementation using the new FD based mount kernel API (ie.,
fsconfig/fsopen) uses MNT_ERR_APPLYFLAGS for failed mount_setattr(2)
calls, which involves more mount attributes (eg., MOUNT_ATTR_RDONLY,
MOUNT_ATTR_NOSUID, etc.) in addition to the MS_PROPAGATION flags (eg.,
MS_SHARED, MS_UNBINDABLE, etc.).
Note that mount_setattr(2) is part of the new FD based mount kernel API,
and is not used by the classic mount(2) based version.
Fallout from 987d844cdb
Signed-off-by: Debarshi Ray <rishi@fedoraproject.org>
tv_usec is only valid in the range [0, 999999].
If the file contains garbage data replace interpret it as "0" instead.
Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
Florian wrote:
after a successful write, cfdisk remains on the "Write" cursor and
furthermore when navigating to "Quit" will continue to show
"...without writing changes", despite there were writes. This patch
addresses that.
Based on patch from Florian Zimmermann <florian.zimmermann@gmail.com>
Signed-off-by: Karel Zak <kzak@redhat.com>
Submission to Project: util-linux
Open Incident: #2325 at github.com/util-linux/util-linux/issues/2325
Component: util-linux/sys-utils
File: dmesg.c
Code level patch applied against: 2.39 - latest code pulled from
git.github.com:util-linux/util-linux.git
BUG: The facility field passed to macro from /usr/include/sys/syslog.h
LOG_MAKEPRI(fac, pri) by dmesg -r needs to have fac argument
shifted 3 bit to the left to return a valid raw valid. The lower
3 bits for a raw value are used by the loglevel priority (pri)
field, so the facility bits can only occupy the bits above the
bits used to hold the pri field value.
The dmesg -r command produces the incorrect output for the raw value
for the or'ed combination of the facility | loglevel priority that gets
produced by the LOG_MAKEPRI macro. That macro is defined as:
#define LOG_MAKEPRI(fac, pri) ((fac) | (pri))
which is defined in the current glibc code in /usr/include/sys/syslog.h
and is used only in the dmesg -r (raw output option) command to form the
raw value for facility or'ed with loglevel priority and displayed as:
<#>[#######.######] ...
where the # in <#> contains the output from the LOG_MAKEPRI macro.
The lower 3 bits are reserved for the loglevel priority 0-7
and the bits above that are for the facility value, so the facility
index should be shifted to the left three bits and or'ed with the
loglevel priority.
In the glibc file: /usr/include/sys/syslog.h the macro LOG_MAKEPRI is
defined as:
#define LOG_MAKEPRI(fac, pri) ((fac) | (pri)
and returns the wrong facility and loglevel priority values, ideally it
should be defined as:
#define LOG_MAKEPRI(fac, pri) ((fac << 3) | (pri))
to return the correct raw value.
We checked with glibc developement and the LOG_MAKEPRI macro is correct
as is and can't be changed as it used by *BSD as is so the solution for
dmesg -r is to shift the facility index left by 3 bits as input to the
LOG_MAKEPRI macro. That is what glibc development recommended.
(For reference, see glibc bugzilla Bug 30563)
We can front end the LOG_MAKEPRI macro with a macro that shifts the
facility by the needed 3 bits which we've added to dmesg.c:
#define LOG_RAW_FAC_PRI(fac, pri) LOG_MAKEPRI((fac << 3), (pri))
This has been tested and works correctly to produce the correct raw
mode value for Facility or'ed together with Loglevel priority.
You can verify that this fix works correctly.
We can test by adding several records to /dev/kmsg like this:
echo "<14> Test Message Facility 8 Loglevel 6" >> /dev/kmsg
echo "<15> Test Message Facility 8 Loglevel 7" >> /dev/kmsg
echo "<30> Test Message Facility 24 Loglevel 6" >> /dev/kmsg
echo "<31> Test Message Facility 24 Loglevel 7" >> /dev/kmsg
these commands add 4 records to the dmesg buffer. Then when we print the
records by cat'ing /dev/kmsg or using the dmesg command several ways:
-bash-4.2# cat /dev/kmsg | grep "Test Message Facility"
14,1114,495317239,-; Test Message Facility 8 Loglevel 6
15,1115,503340779,-; Test Message Facility 8 Loglevel 7
30,1116,643374764,-; Test Message Facility 24 Loglevel 6
31,1117,657165117,-; Test Message Facility 24 Loglevel 7
-bash-4.2# dmesg -x | grep "Test Message Facility"
user :info : [ 495.317239] Test Message Facility 8 Loglevel 6
user :debug : [ 503.340779] Test Message Facility 8 Loglevel 7
daemon:info : [ 643.374764] Test Message Facility 24 Loglevel 6
daemon:debug : [ 657.165117] Test Message Facility 24 Loglevel 7
-bash-4.2# dmesg -S -x | grep "Test Message Facility"
user :info : [ 495.317239] Test Message Facility 8 Loglevel 6
user :debug : [ 503.340779] Test Message Facility 8 Loglevel 7
daemon:info : [ 643.374764] Test Message Facility 24 Loglevel 6
daemon:debug : [ 657.165117] Test Message Facility 24 Loglevel 7
-bash-4.2# dmesg -S -r | grep "Test Message Facility"
<14>[ 495.317239] Test Message Facility 8 Loglevel 6
<15>[ 503.340779] Test Message Facility 8 Loglevel 7
<30>[ 643.374764] Test Message Facility 24 Loglevel 6
<31>[ 657.165117] Test Message Facility 24 Loglevel 7
All the above methods agree in their output as expected.
However, running dmesg -r does not agree.
dmesg -r erronously produces:
----------------------------
-bash-4.2# dmesg -r | grep "Test Message Facility"
<7>[ 495.317239] Test Message Facility 8 Loglevel 6
<7>[ 503.340779] Test Message Facility 8 Loglevel 7
<7>[ 643.374764] Test Message Facility 24 Loglevel 6
<7>[ 657.165117] Test Message Facility 24 Loglevel 7
However, if we run the dmesg -r command using the new front end macro
LOG_RAW_FAC_PRI(fac, pri) we do get the correct output:
Here is the corrected dmesg -r output:
-------------------------------------
-bash-4.2# dmesg -r | grep "Test Message Facility"
<14>[ 495.317239] Test Message Facility 8 Loglevel 6
<15>[ 503.340779] Test Message Facility 8 Loglevel 7
<30>[ 643.374764] Test Message Facility 24 Loglevel 6
<31>[ 657.165117] Test Message Facility 24 Loglevel 7
shifting the facility index value by 3 bits in the LOG_RAW_FAC_PRI macro
provides the correct ouput as shown. All the other commands produce the
same output so now they are all in agreement.
Signed-off-by: Ivan Delalande <colona@arista.com>
Signed-off-by: Edward Chron <echron@arista.com>
* 'lsfd--fix-separators-for-json-output-cleanup' of https://github.com/masatake/util-linux:
lsfd: fix specifying wrong JSON typs when building the help message
tests: (lsfd) add a case for verifying ENDPOINTS column output in JSON mode
* 'PR/libmount-optstr-sync' of github.com:karelzak/util-linux-work:
libmount: add sample to test fs and context relation
libmount: fix sync options between context and fs structs
This makes it easier to run test.sh from the build directory as
everything will work without any parameters irrespective of the build
directories name.
Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
When this option is used nsenter will fetch the parent user
namespace from any namespace file descriptors available.
It can be combined with existing `--user` option in which case
the parent user namespace will be fetched from the user namespace
and replace it.
The usecase of this option is when a user namespace that owns
the other type namespaces we want to switch to is not actually
bound to any process. Without using ioctl it is impossible to
acquire namespace file descriptor. For example, bubblewrap
`bwrap` command creates unbinded user namespace when `--dev`
option is used.
