Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
upstream/upstream_build-sys-do-not-build-plymouth-ctrl.c-w-disabled-pl.patch | [PATCH] build-sys: do not build plymouth-ctrl.c w/ disabled plymouth Do not build plymouth-ctrl.c in agetty and sulogin in case the plymouth support is disabled. |
Pino Toscano <toscano.pino@tiscali.it> | no | 2020-11-17 | ||
upstream/upstream_hwclock-do-not-assume-__NR_settimeofday_time32.patch | [PATCH] hwclock: do not assume __NR_settimeofday_time32 Check that __NR_settimeofday_time32 exists before trying to use it as syscall number. |
Pino Toscano <toscano.pino@tiscali.it> | no | 2020-11-17 | ||
upstream/0001-libmount-don-t-use-symfollow-for-helpers-on-user-mou.patch | [PATCH] libmount: don't use "symfollow" for helpers on user mounts | Karel Zak <kzak@redhat.com> | no | 2020-11-19 | ||
upstream/Manual-pages-document-the-resize-command.patch | Manual pages: document the 'resize' command Reported in https://bugs.debian.org/906918, https://bugs.debian.org/915971. |
Vincent McIntyre <vincent.mcintyre@csiro.au> | no | 2021-01-01 | ||
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 | ||
upstream/libmount-do-not-canonicalize-ZFS-source-dataset.patch | libmount: do not canonicalize ZFS source dataset | Karel Zak <kzak@redhat.com> | no | 2021-01-14 | ||
upstream/libmount-allow-read-only-for-not-root-users.patch | libmount: allow --read-only for not-root users The command "mount -r" was supported for non-root users in very old mount(8) versions. Unfortunately, in this case libmount replaces all mount options from command line by options from fstab. We need exception for MS_RDONLY. |
Karel Zak <kzak@redhat.com> | no | 2021-01-25 | ||
upstream/CVE-2021-37600-sys-utils-ipcutils-be-careful-when-call-calloc.patch | sys-utils/ipcutils: be careful when call calloc() for uint64 nmembs | Karel Zak <kzak@redhat.com> | no | 2021-07-27 | ||
debian/backport-ul_strtou64-function.patch | include/strutils: Add ul_strtou64() function | Salvatore Bonaccorso <carnil@debian.org> | no | backport, https://github.com/util-linux/util-linux/commit/84825b161ba5d18da4142893b9789b3fc71284d9 | ||
upstream/libmount-fix-UID-check-for-FUSE-umount-CVE-2021-3995.patch | [PATCH 1/2] libmount: fix UID check for FUSE umount [CVE-2021-3995] Improper UID check allows an unprivileged user to unmount FUSE filesystems of users with similar UID. |
Karel Zak <kzak@redhat.com> | no | 2021-11-24 | ||
upstream/libmount-fix-deleted-suffix-issue-CVE-2021-3996.patch | [PATCH 2/2] libmount: fix (deleted) suffix issue [CVE-2021-3996] This issue is related to parsing the /proc/self/mountinfo file allows an unprivileged user to unmount other user's filesystems that are either world-writable themselves or mounted in a world-writable directory. The support for "(deleted)" is no more necessary as the Linux kernel does not use it in /proc/self/mountinfo and /proc/self/mount files anymore. |
Karel Zak <kzak@redhat.com> | no | 2022-01-04 | ||
upstream/write-correctly-handle-wide-characters.patch | write: correctly handle wide characters Do this by replacing fputc_careful() (notice that the description said it's locale-aware ‒ it very much is /not/), with a fputs_careful() which does the same thing, but if it were to output a byte in the \123 format, first it checks whether this byte starts a valid multibyte character. If it does, and that character is printable, write it verbatim. This means that echo 'foo åäö ąęćźżń bar' | write nabijaczleweli pts/4 instead of foo \303\245\303\244\303\266 \304\205\304\231\304\207\305\272\305\274\305\204 bar yields foo åäö ąęćźżń bar or, more realistically, from a message I got earlier today, Filip powiedzia\305\202 \305\274e zap\305\202aci jutro becomes Filip powiedział że zapłaci jutro Invalid/non-printable sequences get processed as before. Line reading in write must become getline() to avoid dealing with partial characters: for example on input consisting solely of ąęćźżń, where every {1} is an instance, the output would be {42}ąęć\305\272żń{84}ąęćź\305\274ń{84}ąęćźż\305\204{39} with just fixed-512 fgets() |
=?utf-8?b?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz> | no | debian | 2023-03-15 | |
upstream/wall-convert-homebrew-buffering-to-open_memstream.patch | wall: convert homebrew buffering to open_memstream() The struct buffer system duplicates a plethora of standard I/O functions (including a fork of fputc_careful()) and adds a lot of complexity ‒ open_memstream() is standard, and fits perfectly into this niche |
=?utf-8?b?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz> | no | 2023-03-15 | ||
upstream/wall-use-fputs_careful.patch | wall: use fputs_careful() LINE_MAX only applies to teletypes in canonical mode: when stdin is a file, it could still very much tear; start off at 512 for the sprintf(), then use getline() like in write. The line wrapping has one suboptimal edge-case: $ wall < all Broadcast message from nabijaczleweli@tarta (pts/4) (Tue Mar 14 22:31:25 2023): ^N^O^P^Q^R^S^T^U^V^W^X^Y^Z^[^\^]^^^_ !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJ KLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~^?\200\201\202\203\204\205\206 \207\210\211\212\213\214\215\216\217\220\221\222\223\224\225\226\227\230\231\232 \233\234\235\236\237\240\241\242\243\244\245\246\247\250\251\252\253\254\255\256 \257\260\261\262\263\264\265\266\267\270\271\272\273\274\275\276\277\300\301\302 \303\304\305\306\307\310\311\312\313\314\315\316\317\320\321\322\323\324\325\326 \327\330\331\332\333\334\335\336\337\340\341\342\343\344\345\346\347\350\351\352 \353\354\355\356\357\360\361\362\363\364\365\366\367\370\371\372\373\374\375\376 \377 but that's a pathological input, and the result is still infinitely better than it was before, so fixing that is more trouble than it's worth. |
=?utf-8?b?0L3QsNCx?= <nabijaczleweli@nabijaczleweli.xyz> | no | debian | 2023-03-15 | |
upstream/wall-fix-calloc-cal-Werror-calloc-transposed-args.patch | wall: fix calloc cal [-Werror=calloc-transposed-args] term-utils/wall.c:143:37: error: xcalloc sizes specified with sizeof in the earlier argument and not in the later argument [-Werror=calloc-transposed-args] 143 | buf->groups = xcalloc(sizeof(*buf->groups), buf->ngroups); | ^ term-utils/wall.c:143:37: note: earlier argument should specify number of elements, later size of each element |
Karel Zak <kzak@redhat.com> | no | 2024-01-17 | ||
upstream/wall-fix-escape-sequence-Injection-CVE-2024-28085.patch | wall: fix escape sequence Injection [CVE-2024-28085] Let's use for all cases the same output function. |
Karel Zak <kzak@redhat.com> | no | 2024-03-21 |