summaryrefslogtreecommitdiffstats
path: root/sys-utils
Commit message (Collapse)AuthorAgeFilesLines
...
* misc: consolidate version printing and close_stdout()Karel Zak2019-04-1642-209/+186Star
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* include/c: add print_version() macroKarel Zak2019-04-162-4/+4
| | | | | | | | | | | Let's consolidate the version printing code. It also seems better to use exit() after --version, because it's handled in different way by ASAN. It's strange, but ASAN reports leaks after return in main(). Note that we do not use free-before-exit. Signed-off-by: Karel Zak <kzak@redhat.com>
* chcpu: fix memory leakKarel Zak2019-04-161-4/+5
| | | | | | The CPU set has been allocated more than once. Signed-off-by: Karel Zak <kzak@redhat.com>
* fstrim: get realpath before trim ioctlWang Shilong2019-04-151-2/+9
| | | | | | | | | | | | | | | | | | | | | | Original motivation is we want to run fstrim command on Lustre[1] osd server mount point directly, however our server mount point doesn't export osd directory to users, and it will cause following command fail: $fstrim -v /mnt/mds/ But following succeed: $fstrim -v /mnt/mds We could improve this a bit by getting realpath before trapping kernel, this also give benifits to normal use cases. Cc: Andreas Dilger <adilger@dilger.ca> Cc: Shuichi Ihara <sihara@ddn.com> [1] http://wiki.lustre.org/Main_Page Signed-off-by: Wang Shilong <wshilong@ddn.com>
* lscpu: wrap default output long lines on terminalKarel Zak2019-04-112-2/+5
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: report CPU vulnerabilitiesKarel Zak2019-04-112-0/+80
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* setarch: add new e2k subarchesAndrew Savchenko2019-04-091-0/+13
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* fstrim.c: Remove commnet about vfat not supporting fstrimMarcos Paulo de Souza2019-04-011-1/+1
| | | | | | | Commit f663b5b38f ("fat: add FITRIM ioctl for FAT file system") in linux kernel added support for using fstrim with vfat filesystem. Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
* lscpu: (man) tiny changesKarel Zak2019-03-191-2/+2
|
* lscpu: fix excl[] array orderKarel Zak2019-03-191-1/+1
| | | | | | It (rows and columns) must be in ASCII order. Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: fix and document --output-allKarel Zak2019-03-191-2/+3
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: define libsmartcols flags for -eKarel Zak2019-03-191-10/+10
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: fix --caches orderKarel Zak2019-03-191-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: (man) make SYNOPSIS compatible with another utilsKarel Zak2019-03-191-4/+1Star
| | | | | | In this case is really no reason to duplicate all options in SYNOPSIS. Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: add --bytesKarel Zak2019-03-192-10/+26
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: add --cachesKarel Zak2019-03-193-38/+231
| | | | | | | | | | | | | | | $ lscpu -C NAME ONE-SIZE ALL-SIZE WAYS TYPE LEVEL L3 8M 8M 16 Unified 3 L2 256K 1M 8 Unified 2 L1i 32K 128K 8 Instruction 1 L1d 32K 128K 8 Data 1 The patch also updates extra caches (s390) output in lsblk summary to be compatible with output about normal caches. Addresses: https://github.com/karelzak/util-linux/issues/663 Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: rename macros and functionsKarel Zak2019-03-191-77/+77
| | | | | | | We need to differentiate between output about CPUs and another stuff (caches in future). Let's make it more obvious in code. Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: report more usable cache sizesKarel Zak2019-03-191-2/+41
| | | | | | | | | | | | | | | | | The current version reports cache size as reported by /sys, it means real size of the one piece of the cache. This way provides minimal overview about all system as the cache is often shared between CPUs. It seems better to report all size of the caches in the summary output. It also does not make sense to report sizes per core (or socket) as CPU topology may be pretty complicated. The final solution (not implemented yet) will be to have --list-caches where we can report all details like all-size, item-size, per-core size, ways, type, etc. Addresses: https://github.com/karelzak/util-linux/issues/663 Signed-off-by: Karel Zak <kzak@redhat.com>
* lscpu: add 'Frequency boost'Karel Zak2019-03-152-0/+8
| | | | | | | | Show turbo boost status on platforms where is available a file /sys/devices/system/cpu/cpufreq/boost. Addresses: https://github.com/karelzak/util-linux/issues/755 Signed-off-by: Karel Zak <kzak@redhat.com>
* swapon.8: mention btrfs(5)Marcos Mello2019-03-111-15/+14Star
| | | | | | See: https://github.com/kdave/btrfs-progs/commit/5c880c82c2044b0abae5c838c733a2e6522ed122
* Update mount.8MeggyCal2019-03-071-1/+1
| | | xfs is widely supported today
* lscpu: document --hex output regression (since v2.30)Karel Zak2019-02-201-2/+3
| | | | | Addresses: https://github.com/karelzak/util-linux/issues/744 Signed-off-by: Karel Zak <kzak@redhat.com>
* docs: fix typos [codespell]Sami Kerola2019-02-181-1/+1
| | | | | Reference: https://github.com/codespell-project/codespell Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* various: fix 'uninitialized when used' warnings [clang]Sami Kerola2019-02-183-3/+3
| | | | | | | This change fixes "warning: variable 'var' may be uninitialized when used here [-Wconditional-uninitialized]" warnings reported in various files. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* mount: Do not call mnt_pretty_path() on net file systems.Stanislav Brabec2019-02-061-1/+1
| | | | | | | | | | | | Calling mnt_pretty_path() on network file systems can cause mangling of the output: root# mount | grep nfs nfs.example.com:/home on /home type nfs4 ... root# mkdir -p nfs.example.com:/home root# mount | grep nfs /root/nfs.example.com:/home on /home type nfs4 ... Signed-off-by: Stanislav Brabec <sbrabec@suse.cz>
* mount.8: clarify (no)suid behavior on file capabilitiesPeter Wu2019-02-011-4/+4
| | | | | | | | | | Clarify that the nosuid option also affects file capabilities and that it only limits execution of programs. (setgid on directories still inherit the group regardless of the nosuid option.) The new text is taken from the mount(2) manual page from the man-pages project. Addresses: https://github.com/karelzak/util-linux/issues/482 Signed-off-by: Peter Wu <peter@lekensteyn.nl>
* setarch: don't return address of automatic variableAndreas Schwab2019-01-221-1/+1
| | | | | | | | | | | On architectures without special personalities setarch uses the contents of a local variable with automatic storage duration after return from the function, causing it to report a spurious error. $ setarch m68k setarch: Kernel cannot set architecture to m68k Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
* losetup: update an error messageJeffrey Ferreira2019-01-221-1/+1
| | | | | | | | Update an error message to add --partscan to the list of options only allowed during loop device setup. Signed-off-by: Jeffrey Ferreira <jeffpferreira@gmail.com> Signed-off-by: Karel Zak <kzak@redhat.com>
* losetup: properly use --sector-size when create a new deviceKarel Zak2019-01-222-18/+22
| | | | | | | | | | | | | The --partscan functionality depends on sector size. Make sure sector size is set before we force kernel to scan the device for partitions. For example: losetup -f loopfile --sector-size 4KiB --partscan --show where 'loopfile' contains GPT with 4096 sectors. Reported-by: Jeffrey Ferreira <jeffpferreira@gmail.com> Signed-off-by: Karel Zak <kzak@redhat.com>
* lib/loopdev: differentiate between setter()s and ioctl callsKarel Zak2019-01-221-4/+4
| | | | | | | | Now the internal API uses loopcxt_set_...() to set context variables as well as to call ioctls. This patch introduces loopcxt_ioctl_...() to makes things more obvious to readers. Signed-off-by: Karel Zak <kzak@redhat.com>
* swapon: be more explicit about BTRFSKarel Zak2019-01-221-3/+4
| | | | | | | | It seems nocow and nodatasum attributes are required. See btrfs_swap_activate() in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed46ff3d423780fa5173b38a844bf0fdb210a2a7 Addresses: https://github.com/karelzak/util-linux/issues/633 Signed-off-by: Karel Zak <kzak@redhat.com>
* swapon: rewrite section about swapfilesKarel Zak2019-01-221-24/+21Star
| | | | | | | | | | | | * don't duplicate info on two places -- let's keep only small note in mkswap(8) man page, suggest to read swapon(8) man page * add info about kernel versions for XFS and Btrfs swapfiles support * use subsection in the NOTES Addresses: https://github.com/karelzak/util-linux/issues/633 Signed-off-by: Karel Zak <kzak@redhat.com>
* swapon: (man) cleanup note about holesKarel Zak2019-01-211-11/+9Star
| | | | | Addresses: https://github.com/karelzak/util-linux/issues/633 Signed-off-by: Karel Zak <kzak@redhat.com>
* mount: (man) add note about --all to remount descKarel Zak2019-01-211-0/+12
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* losetup: use offset in warn_size() calculationKarel Zak2019-01-181-2/+5
| | | | | | | | | | | | | | | | | | # dd if=/dev/urandom of=dummy bs=513 count=1 2>/dev/null # losetup -f --show --offset 1 dummy /dev/loop0 losetup: dummy: Warning: file does not fit into a 512-byte sector; the end of the file will be ignore The warning is bogus as with offset the size of the file fits into 512-byte sector. Simple test that all is right: # dd if=dummy bs=1 skip=1 2>/dev/null | sha256sum - /dev/loop0 da2ed0ade6ea518a802cd8a7a3c01c408ad8699ef6856b0b01f92b867d4ba9b5 - da2ed0ade6ea518a802cd8a7a3c01c408ad8699ef6856b0b01f92b867d4ba9b5 /dev/loop0 Addresses: https://github.com/karelzak/util-linux/issues/722 Signed-off-by: Karel Zak <kzak@redhat.com>
* libmount: add support for MS_REMOUNT on --allKarel Zak2019-01-162-1/+59
| | | | | | | | | | | | | This patch add to support for remount-all operation to libmount and mount(8). For example: mount --all -o remount,ro -t vfat to remount read-only all VFAT filesystems. Addresses: https://github.com/karelzak/util-linux/issues/589 Signed-off-by: Karel Zak <kzak@redhat.com>
* build-sys: use REALTIME_LIBS for hwclock due to monotonic.cKarel Zak2019-01-141-1/+2
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* Merge branch 'time-fixes' of https://github.com/kerolasa/util-linuxKarel Zak2019-01-142-3/+6
|\ | | | | | | | | | | | | | | * 'time-fixes' of https://github.com/kerolasa/util-linux: fsck.cramfs: use utimes() instead of utime() that is obsolete hwclock: use monotonic time to measure how long setting time takes include: add indirect monotonic clock id specifier timeutils: match today day and this year correctly
| * hwclock: use monotonic time to measure how long setting time takesSami Kerola2019-01-122-3/+6
| | | | | | | | | | | | | | | | | | Earlier gettimeofday() was affected by discontinuous jumps. Measuring how long time it takes to set time using function that effected by the very thing being measured makes head spin. Lets make this less confusing with monotonic clock that ticks on without jumps. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* | readprofile: check input file is not empty [asan]Sami Kerola2019-01-131-0/+2
|/ | | | | Addresses: https://github.com/karelzak/util-linux/issues/717 Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* fstrim: check for read-only devices on -a/-AKarel Zak2019-01-111-2/+4
| | | | | | | to avoid "FITRIM ioctl failed: Remote I/O error" Addresses: https://github.com/karelzak/util-linux/issues/738 Signed-off-by: Karel Zak <kzak@redhat.com>
* ldattach: Check for value of _HAVE_STRUCT_TERMIOS_C_ISPEEDKhem Raj2019-01-051-1/+1
| | | | | | | | | | in glibc 2.29+ checking for just existence of _HAVE_STRUCT_TERMIOS_C_ISPEED won't be enough, the value has to be checked see https://sourceware.org/git/?p=glibc.git;a=commit;h=e5a50db36eaa6e8c6427b3a971563240b633ca85 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* chmem: add initilizer [clang]Sami Kerola2019-01-021-1/+1
| | | | | | warning: use of GNU empty initializer extension [-Wgnu-empty-initializer] Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* Remove duplicate entry for reset-env from usageJohn W Higgins2018-12-181-1/+0Star
| | | I assume the second entry was not desired in the original commit. Line 153-154 would appear to be a duplicate
* dmesg: correct "-n, --console-level level" example in manual pageJean-Philippe ROMAIN2018-12-171-1/+1
| | | | | | | | | | When providing an abbreviation of the level name with the option "-n, --console-level level", it corresponds to the level (included) up to which messages are displayed on the console. If a level number is given, this level is excluded. So in the given example, "-n 1" is equivalent to "-n emerg". Signed-off-by: Jean-Philippe Romain <jean-philippe.romain@st.com>
* lscpu: Add aarch32 detection on aarch64Jeremy Linton2018-12-111-0/+14
| | | | | | | | | aarch32 support is an optional feature of ARMv8, as CPUs which don't support aarch32 become more common, lets make sure that lscpu can tell a user quickly if they are on a machine that only supports 64-bit. Signed-off-by: Jeremy Linton <lintonrjeremy@gmail.com>
* umount: fix --quietKarel Zak2018-12-101-1/+1
| | | | | Addresses: https://github.com/karelzak/util-linux/commit/d5fd9ac6b208c5acdb6c0023757a7e2827474482#commitcomment-31610748 Signed-off-by: Karel Zak <kzak@redhat.com>
* choom: fix negative adjust score usageKarel Zak2018-12-101-1/+1
| | | | | | | | It's really bad idea to use uint64_t (ul_path_write_u64(()) when write signed number. Addresses: https://github.com/karelzak/util-linux/issues/723 Signed-off-by: Karel Zak <kzak@redhat.com>
* fstrim: fix usage()Karel Zak2018-12-101-1/+1
| | | | Signed-off-by: Karel Zak <kzak@redhat.com>
* fstrim: trim also root FS on --fstabKarel Zak2018-12-102-1/+19
| | | | | | | | | The root fs ("/") is optional in many case in /etc/fstab. This patch forces fstrim to read kernel command line for the root= option to get root FS if the entry is missing in your fstab. Addresses: https://github.com/karelzak/util-linux/issues/719 Signed-off-by: Karel Zak <kzak@redhat.com>
generated by cgit v1.2.3-55-g7522 (git 2.39.0) at 2024-05-25 21:40:59 +0200