| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| debian/man-getopt-examples.patch | util-linux: getopt(1) should point to where examples are on a Debian system Debian BTS #913049 |
Matthew Vernon <matthew@debian.org> | no | 2018-11-06 | ||
| debian/verbose-tests.patch | verbose-tests Enable verbose tests and print content of failing tests output file. |
Andreas Henriksson <andreas@fatal.se> | no | 2014-07-30 | ||
| debian/hardlink-tests-known-failed.patch | hardlink tests: set known failed sha256 cannot be initialized on some archs / buildds. |
Chris Hofstaedtler <zeha@debian.org> | no | 2022-04-12 | ||
| debian/lsfd-usrbin.patch | Install lsfd into /usr/bin | Chris Hofstaedtler <zeha@debian.org> | no | 2022-04-14 | ||
| debian/sensible-pager.patch | Use sensible-pager | Chris Hofstaedtler <zeha@debian.org> | no | 2022-07-14 | ||
| debian/Skip-tmpfs-sensitive-tests-if-fstype-cannot-be-determined.patch | Skip tmpfs-sensitive tests if fstype cannot be determined https://github.com/util-linux/util-linux/issues/3266 Debian bug #1086706 |
Chris Hofstaedtler <zeha@debian.org> | no | 2024-11-13 | ||
| debian/login-support-LOG_OK_LOGINS.patch | login: support LOG_OK_LOGINS | Chris Hofstaedtler <zeha@debian.org> | no | 2024-08-05 | ||
| debian/login-do-not-print-motd-done-by-PAM.patch | login: do not print motd, done by PAM | Chris Hofstaedtler <zeha@debian.org> | no | 2024-08-05 | ||
| debian/login-turn-off-btmp-utmp-lastlog-writing.patch | login: turn off btmp, utmp, lastlog writing Should be done by PAM instead. login from src:shadow had turned it off, especially with --enable-logind. |
Chris Hofstaedtler <zeha@debian.org> | no | 2024-08-05 | ||
| upstream-master/audit-arch.h-add-defines-for-m68k-sh.patch | audit-arch.h: add defines for m68k, sh John Paul Adrian Glaubitz points out that libseccomp needs to release 2.6.0, too. Upstream commit 5ebf0edb0a0531cba801c7791543c610725bf944. |
Chris Hofstaedtler <zeha@debian.org> | no | 2024-04-09 | ||
| upstream-master/fsck-warn-if-fsck.-type-not-found-and-device-is-specified.patch | fsck: warn if fsck.<type> not found and device is specified The fsck(8) command prints an error for certain 'required' filesystems, such as extN, if the corresponding fsck.<type> helper is not found. However, for other filesystems, it silently ignores the device. While this behavior is acceptable for the -A option, if a user explicitly specifies the device on the command line, it is probably a good idea to be more verbose and issue a warning that the device will be ignored. The warning is enabled only for interactive mode (only one device specified or -s). Note that some filesystems do not have an fsck utility, so caution is needed when issuing such warnings to prevent the generation of a large number of unwanted entries in system logs, etc." |
Karel Zak <kzak@redhat.com> | no | 2024-02-08 | ||
| upstream-master/libmount-Fix-atime-remount-for-new-API.patch | libmount: Fix atime remount for new API All atime settings are mutually exclusive, and the attr_set mask for the mount_setattr() syscall cannot contain multiple MOUNT_ATTR_ atime related options. Unfortunately, during a remount, the list of options is composed of both old and new options. In this case, libmount sets more atime options to the mask. The correct behavior is to use the last atime related option from the list. |
Karel Zak <kzak@redhat.com> | no | 2024-05-14 | ||
| upstream-master/swapoff-avoid-being-killed-by-OOM.patch | swapoff: avoid being killed by OOM Based on patch from dparalen <vetrisko@gmail.com>. |
Karel Zak <kzak@redhat.com> | no | 2024-06-20 | ||
| upstream-master/unshare-mount-binfmt_misc.patch | unshare: mount binfmt_misc add --mount-binfmt[=<dir>] to mount binfmt_misc filesystem, this results in clearing inherited interpreters from the previous namespace |
Laurent Vivier <laurent@vivier.eu> | no | 2024-06-19 | ||
| upstream-master/unshare-load-binfmt_misc-interpreter.patch | unshare: load binfmt_misc interpreter add -l, --load-interp <file> to load a binfmt_misc interpreter at startup. The interpreter is loaded from the initial fileystem if the 'F' flags is provided, otherwise from inside the new namespace This makes possible to start a chroot of another architecture without being root. |
Laurent Vivier <laurent@vivier.eu> | no | 2024-06-19 | ||
| upstream-master/agetty-add-systemd-to-version-output.patch | agetty: add "systemd" to --version output | Karel Zak <kzak@redhat.com> | no | 2024-07-11 | ||
| upstream-master/Treat-out-of-memory-as-error.patch | Treat out of memory as error Otherwise it might happen that a configured file location is not taken into account. A NULL value would lead to default file location. |
Tobias Stoeckmann <tobias@stoeckmann.org> | no | 2024-08-12 | ||
| upstream-master/more-make-sure-we-have-data-on-stderr.patch | more: make sure we have data on stderr more(1) uses more_poll() to monitor data on stdin, stderr, and signals. It is used before read_command(), but this function only reads from stderr. Therefore, if any other non-stderr event occurs, this function will wait on read(). In this case, more(1) will not react to signals anymore. We need to ensure that more(1) only waits in more_poll(). Try for x in {1..1000}; do echo "line $x"; done | more to reproduce. |
Karel Zak <kzak@redhat.com> | no | 2024-08-22 | ||
| upstream-master/lscpu-optimize-query-virt-pci-device.patch | lscpu: optimize query virt pci device The lscpu command needs to traverse the /proc/bus/pci/devices file three times to check for any PCI devices related to virtualization. If there are many PCI devices on the machine, this can lead to increased execution time for lscpu. It would be beneficial to consolidate these queries into a single check to optimize the execution time of lscpu. Use time command to test on a machine with 13000 PCI devices: before: real 0m13.506s user 0m0.028s sys 0m13.409s after: real 0m5.834s user 0m0.018s sys 0m5.771s |
Guixin Liu <kanie@linux.alibaba.com> | no | 2024-08-21 | ||
| upstream-master/Optionally-execute-a-program-after-group-change.patch | Optionally execute a program after group change We accept a `-c` command option or possible second argument which is then invoked through the user's shell after the group change, as by the `sg` utility. The default is still running the shell itself. |
=?utf-8?b?R8OhYm9yIE7DqW1ldGg=?= <homar@riseup.net> | no | 2024-08-29 | ||
| upstream-master/logger-correctly-format-tv_usec.patch | logger: correctly format tv_usec tv_usec is an unspecified signed integer type. The format string %u assumes an unsigned int, which is incorrect. Especially on 32bit big-endian, where it can lead to invalid values. |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-04-09 | ||
| upstream-master/lsclocks-fix-dynamic-clock-ids.patch | lsclocks: fix dynamic clock ids Without an explicitly specified clock id, lsclocks would always use clock id 0 (CLOCK_REALTIME) for the dynamic/PTP clocks. |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-12-24 | ||
| upstream-master/fincore-Use-correct-syscall-number-for-cachestat-on-alpha.patch | fincore: Use correct syscall number for cachestat on alpha Fixes #3331, #3333 |
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> | no | 2024-12-25 | ||
| upstream-master/tests-fdisk-bsd-Update-expected-output-for-alpha.patch | tests: fdisk/bsd: Update expected output for alpha Fixes #3332 |
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> | no | 2024-12-25 | ||
| upstream-master/lscpu-Add-FUJITSU-aarch64-MONAKA-cpupart.patch | lscpu: Add FUJITSU aarch64 MONAKA cpupart Add an entry for FUJITSU aarch64 part MONAKA. |
"Emi, Kisanuki" <fj0570is@fujitsu.com> | no | 2024-12-24 | ||
| upstream-master/libblkid-fix-spurious-ext-superblock-checksum-mismatches.patch | libblkid: fix spurious ext superblock checksum mismatches Reads of ext superblocks can race with updates. If libblkid observes a checksum mismatch, re-read the superblock with O_DIRECT in order to get a consistent view of its contents. Only if the O_DIRECT read fails the checksum should it be reported to have failed. This fixes a problem where devices that were named by filesystem label failed to be found when systemd attempted to mount them on boot. The problem was caused by systemd-udevd using libblkid. If a read of a superblock resulted in a checksum mismatch, udev will remove the by-label links which result in the mount call failing to find the device. The checksum mismatch that was triggering the problem was spurious, and when we use O_DIRECT, or even perform a subsequent retry, the superblock is correctly read. This resulted in a failure to mount /boot in one out of every 2,000 or so attempts in our environment. e2fsprogs fixed[1] an identical version of this bug that afflicted resize2fs during online grow operations when run from cloud-init. The fix there was also to use O_DIRECT in order to read the superblock. This patch uses a similar approach: read the superblock with O_DIRECT in the case where a bad checksum is detected. [1] https://lore.kernel.org/linux-ext4/20230609042239.GA1436857@mit.edu/ |
Krister Johansen <kjlx@templeofstupid.com> | no | 2024-11-18 | ||
| upstream-master/login-utils-su-common-Check-that-the-user-didn-t-change-d.patch | login-utils/su-common: Check that the user didn't change during PAM transaction PAM modules can change the user during their execution, in such case su would still use the user that has been provided giving potentially access to another user with the credentials of another one. So prevent this to happen, by ensuring that the final PAM user is matching the one required |
=?utf-8?b?Ik1hcmNvIFRyZXZpc2FuIChUcmV2acOxbyki?= <mail@3v1n0.net> | no | 2024-09-20 | ||
| upstream-master/login-utils-su-common-Validate-all-return-values-again.patch | login-utils/su-common: Validate all return values again The additional coded added in commit d6564701e812 ("login-utils/su-common: Check that the user didn't change during PAM transaction") was inserted in between the assignment and tests of "rc", making the return value unchecked. Add a new explicit check. |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-09-25 | ||
| upstream-master/sys-utils-setpriv-fix-potential-memory-leak.patch | sys-utils: (setpriv): fix potential memory leak Dynamic memory, referenced by 'buf' is allocated by calling function 'xstrdup' add then changed by calling of strsep function. The free(buf) call is incorrect if buf != NULL, and points to some place inside or outside the source string. |
Maks Mishin <maks.mishinFZ@gmail.com> | no | 2024-10-10 | ||
| upstream-master/lscpu-fix-incorrect-number-of-sockets-during-hotplug.patch | lscpu: fix incorrect number of sockets during hotplug lscpu sometimes shows incorrect 'Socket(s)' value if a hotplug operation is running. On a 32 CPU 2-socket system, the expected output is as shown below: Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Model name: POWER10 (architected), altivec supported Thread(s) per core: 8 Core(s) per socket: 2 Socket(s): 2 On the same system, if hotplug is running along with lscpu, it shows "Socket(s):" as 3 and 4 incorrectly sometimes. Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-11,16-31 Off-line CPU(s) list: 12-15 Model name: POWER10 (architected), altivec supported Thread(s) per core: 8 Core(s) per socket: 1 Socket(s): 3 The number of sockets is considered as the number of unique core_siblings CPU groups. The issues causing the number of sockets to sometimes be higher during hotplug is: 1. The core_siblings of CPUs on the same socket are different because a CPU on the socket has been onlined/offlined in between. In the below example, nr sockets was wrongly incremented for CPU 5 though CPU 4 and 5 are on the same socket because their core_siblings was different as CPU 12 was onlined in between. core_siblings: ff f0 0 0 0 0 0 0 core_siblings: ff f8 0 0 0 0 0 0 2. The core_siblings file of a CPU is created when a CPU is onlined. It may have an invalid value for some time until the online operation is fully complete. In the below example, nr sockets is wrongly incremented because the core_siblings of CPU 14 was 0 as it had just been onlined. core_siblings: 0 0 0 0 0 0 0 0 To fix this, make the below changes: 1. Instead of considering CPUs to be on different sockets if their core_siblings masks are unequal, consider them to be on different sockets only if their core_siblings masks don't have even one common CPU. Then CPUs on the same socket will be correctly identified even if offline/online operations happen while they are read if at least one CPU in the socket is online during both reads. 2. Check if a CPU's hotplug operation has been completed before using its core_siblings file [kzak@redhat.com: - use xmalloc(), - use ul_strtos32(), - use err() on CPU_ALLOC() error] |
Anjali K <anjalik@linux.ibm.com> | no | 2024-11-04 |