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/tests-mark-lsfd-tests-failing-in-sbuild.patch | tests: mark lsfd mkfds-socketpair as failing in sbuild | Chris Hofstaedtler <zeha@debian.org> | no | 2024-02-29 | ||
upstream/lsfd-add-LSFD_DEBUG-env-var-for-debugging.patch | lsfd: add LSFD_DEBUG env var for debugging | Masatake YAMATO <yamato@redhat.com> | no | 2024-03-30 | ||
upstream/tests-test_mkfds-sockdiag-verify-the-recived-message.patch | tests: (test_mkfds::sockdiag) verify the recived message | Masatake YAMATO <yamato@redhat.com> | no | 2024-04-02 | ||
debian/tests-mark-fadvise-drop-as-known-failing-on-buildds.patch | tests: mark fadvise/drop as known failing on buildds buildds build on a tmpfs, but this is not visible inside the build environment. |
Chris Hofstaedtler <zeha@debian.org> | no | 2024-04-02 | ||
upstream/tests-lsfd-mkfds-multiplexing-skip-if-proc-pid-syscall-is.patch | tests: (lsfd::mkfds-multiplexing) skip if /proc/$pid/syscall is broken Close #2867 Close #2887 We should skip the test case on the platforms where /proc/$pid/syscall doesn't report correct system call number. On such platforms, |
Masatake YAMATO <yamato@redhat.com> | no | 2024-04-05 | ||
upstream/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/Revert-lib-pager-Apply-pager-specific-fixes-only-when-nee.patch | Revert "lib/pager: Apply pager-specific fixes only when needed" Less is not always detectable, as it can be hidden behind symlinks or wrapper as for example in a default Debian installation. Also testing for the literal string "less" does not match full path specifications like "/usr/bin/less". Instead always apply the fixes. This reverts commit c10ad975895372122f72c8d9da089b6ea69f778b. Closes #2951 |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-04-13 | ||
upstream/libblkid-Fix-segfault-when-blkid.conf-doesn-t-exist.patch | libblkid: Fix segfault when blkid.conf doesn't exist * Move 'line' and 'uevent' to the beginning of the LIBECONF code. * Remove unwanted space between function name and arguments. * Check for 'line' pointer before dereferencing. (cherry picked from commit 7e357241b413a01c37b0b4d064bc0a47e3259361) |
Karel Zak <kzak@redhat.com> | no | 2024-04-01 | ||
upstream/pam_lastlog2-link-against-liblastlog.patch | pam_lastlog2: link against liblastlog While at it also drop the duplicated include path. Fixes #2897 (cherry picked from commit 2722b40012740372daf3585b7c071fcbede13359) |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-04-01 | ||
upstream/libblkid-topology-ioctl-correctly-handle-kernel-types.patch | libblkid: topology/ioctl: correctly handle kernel types Commit 5d71d711d07a ("libblkid: topolicy/ioctl: use union for multiple data types") incorrectly assumed that set_ulong and set_int refer to the type returned by the kernel. Instead the different function pointer names refer to the types of the function pointers. However all ioctls, except for the later added BLKGETDISKSEQ, return 32bit integers. This made libblkid also interpret the upper 32bits too, leading to garbage values. Introduce a new member 'kernel_size' to also handle the 64bit BLKGETDISKSEQ. Drop data.ul as it is no actually used. Closes #2904 (cherry picked from commit a10081a52c48a5232db30d8e0a7a7570cc8163ae) |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-04-02 | ||
upstream/libblkid-topology-ioctl-simplify-ioctl-handling.patch | libblkid: topology/ioctl: simplify ioctl handling Coverity complains about the data copy within the union. Instead unroll the loop which is less code and easier to follow. (cherry picked from commit 2ab95860db0b7423906911b8b9e9f231332c2c11) |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-04-04 | ||
upstream/findmnt-revise-the-code-for-I-and-D-option.patch | findmnt: revise the code for -I and -D option Fixes #2913. 3dd79293b5b655da9d913dedd8facb08959a7826 added -I option. However, the code used bit flags (FL_DF and FL_DF_INODES) wrongly; the code broke the output of -D option. (cherry picked from commit aa0c45e8686df509c169121473d2cfb4fe18c3ea) |
Masatake YAMATO <yamato@redhat.com> | no | 2024-04-05 | ||
upstream/Fix-misplaced-else-in-mnt_update_already_done.patch | Fix misplaced else in mnt_update_already_done See 477401f0de (cherry picked from commit 6b316e0c9f1feb61bef3bb14b1356be8fbefcc17) |
Gavin Lloyd <gavinhungry@gmail.com> | no | 2024-04-09 | ||
upstream/lsns-report-with-warnx-if-a-namespace-related-ioctl-fails.patch | lsns: report with warnx if a namespace related ioctl fails with ENOSYS Qemu userspace emulation reports ENOSYS if it doesn't support a given ioctl command. (cherry picked from commit 0a7a8fbc7a82dfbd9e925d1b4d4936bf4e011bc1) |
Masatake YAMATO <yamato@redhat.com> | no | 2024-04-15 | ||
upstream/lsns-tolerate-lsns_ioctl-fd-NS_GET_-PARENT-USERNS-failing.patch | lsns: tolerate lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failing with ENOSYS With the original code, "lsns/filedesc" test case failed on "build (qemu-user, s390x)" and "build (qemu-user, riscv64)". On the platforms, lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failed with ENOSYS. The error stoped the iteration for gathering information from /proc/[0-9]+. As a result, lsns printed nothing. We don't expect this behavior. (cherry picked from commit f2a8b20d9c63f771d1fddd639ea1ec3fe034dc6d) |
Masatake YAMATO <yamato@redhat.com> | no | 2024-04-14 | ||
upstream/lslocks-don-t-abort-gathering-per-process-information-eve.patch | lslocks: don't abort gathering per-process information even if opening a /proc/[0-9]* fails If a process ($pid) taking a lock is gone while running lslocks, gathering per-process information for the process may fail in opening /proc/$pid. Though lslocks should work with incomplete information, the original code stopped gathering per-process information for the other processes. As a result of the original behavior, tests/ts/lslocks/lslocks really failed in an environment where multiple test cases ran simultaneously. Close #2624 again. See also #2633. (cherry picked from commit 20df923cc3d2da12a5296223c3ff0de7484cc587) |
Masatake YAMATO <yamato@redhat.com> | no | 2024-04-13 | ||
upstream/lslocks-remove-a-unused-local-variable.patch | lslocks: remove a unused local variable (cherry picked from commit c8c85e8e54aa201766f2420e2a7c86ccfa8d5df0) |
Masatake YAMATO <yamato@redhat.com> | no | 2024-04-13 | ||
upstream/libsmartcols-reset-wrap-after-calculation.patch | libsmartcols: reset wrap after calculation (cherry picked from commit 62f64717ec134b10c5a670403c2d8c43b608e671) |
Karel Zak <kzak@redhat.com> | no | 2024-04-16 | ||
upstream/agetty-Don-t-override-TERM-passed-by-the-user.patch | agetty: Don't override TERM passed by the user Before 4869b259d68f65ea88df625ce8df9c0177d55a01, any TERM passed on the agetty command line would be used instead of the default TERM. After 4869b259d68f65ea88df625ce8df9c0177d55a01, the default TERM is used unconditionally. Fix the regression by checking if the user passed a custom TERM. (cherry picked from commit af354e92111769d57e43eb4f1825c0d99c894ddb) |
Daan De Meyer <daan.j.demeyer@gmail.com> | no | 2024-04-19 | ||
upstream/findmnt-always-zero-terminate-SOURCES-data.patch | findmnt: always zero-terminate SOURCES data libsmartcols expects it's data fields to be zero terminated. See the call to strlen() in scols_column_greatest_wrap(). ul_buffer however does not guarantee that termination, ul_buffer_append_strings() discard the zero-termination. Always zero-terminate in get_data_col_sources() and drop the now unnecessary variable "i". (cherry picked from commit 6594679e9af805075c282da35b1b2a8d767e403b) |
=?utf-8?q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de> | no | 2024-04-21 | ||
upstream/lsblk-simplify-SOURCES-code.patch | lsblk: simplify SOURCES code This complicated implementation originated from an early version of zero-separated items for libsmartcols. It is no longer necessary. (cherry picked from commit af4c7dac191abadc33aae75916583c890cd2ebc3) |
Karel Zak <kzak@redhat.com> | no | 2024-04-22 | ||
upstream/libmount-Fix-access-check-for-utab-in-context.patch | libmount: Fix access check for utab in context The function mnt_has_regular_utab() properly detects that the utab is not writable, but this is ignored by the high-level context API. As a result, the library later attempts to update the file and ends up with a warning in mount(8): $ mkdir sys $ unshare --map-root-user --mount $ mount --rbind /sys sys $ umount --lazy sys; echo $? umount: /home/user/sys: filesystem was unmounted, but failed to update userspace mount table. 16 In this case, the utab should be ignored. (cherry picked from commit 97f7bfc0fdf74b6a6e220ba9d2f620386e660b29) |
Karel Zak <kzak@redhat.com> | no | 2024-04-22 | ||
upstream/libmount-fix-comment-typo-for-mnt_fs_get_comment.patch | libmount: fix comment typo for mnt_fs_get_comment() (cherry picked from commit c630dbc38f7cd1f838e65e2c43d8375bce1ec20f) |
Tianjia Zhang <tianjia.zhang@linux.alibaba.com> | no | 2024-04-22 | ||
upstream/lsns-fix-netns-use.patch | lsns: fix netns use # ip netns add vpn # lsns -T -t net Segmentation fault (core dumped) The function interpolate_missing_namespaces() reads data from /proc. However, in the case of a persistent namespace, there is no procfs entry for the namespace. Therefore, this function should ignore it. (cherry picked from commit 42880f54894c1d7fd113552ff8474566a2595a0d) |
Karel Zak <kzak@redhat.com> | no | 2024-04-22 |