Debian Patches
Status for hurd/1:0.9.git20260527-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| diskfs_no_inherit_dir_group.patch | Follow POSIX rules for gid of new nodes. | no | ||||
| init_try_runsystem.gnu.patch | Also try runsystem.sysv, in case /etc/alternatives/runsystem is hosed. | no | ||||
| rc.patch | More debianish rc scripts | no | ||||
| startup-usr-support.patch | Debian GNU/Hurd has a real /usr | no | ||||
| uptime_w_path_fix.patch | Debian has a real /usr and uses w-hurd file name | no | ||||
| stat_round.patch | This is not a proper fix, discussed on http://lists.gnu.org/archive/html/bug-hurd/2009-02/msg00002.html but not finished, last mail on http://lists.gnu.org/archive/html/bug-hurd/2009-04/msg00006.html We should support i_ctime_extra/i_mtime_extra/i_atime_extra anyway. |
no | ||||
| external.patch | Include DDE in the build =================================================================== |
no | ||||
| console_ignore_bdf_err.patch | reduce-font overestimates the number of characters in the font. This should be fixed there, not here. diff --git a/console-client/bdf.c b/console-client/bdf.c index 30501f4..ee8aa30 100644 |
no | ||||
| libexec.patch | =================================================================== | no | ||||
| mount.patch | * utils/mount.c (do_mount): Ignore `loop' and `exec' options. | no | ||||
| MAKEDEV-apm.patch | Workaround invocations from installation of power-management packages. =================================================================== |
no | ||||
| term-for-tcl.patch | See discussion in http://bugs.debian.org/755295 and bug report on comp.lang.tcl on July 1st 2015 (“'expect' losing data due to tcl buffering”) |
no | ||||
| crash-logging.patch | xxx crash logging works | no | ||||
| libports-iterate-refcount.patch | http://lists.gnu.org/archive/html/bug-hurd/2016-03/msg00034.html diff --git a/libports/bucket-iterate.c b/libports/bucket-iterate.c index b021b99..76dc3f7 100644 |
no | ||||
| io-write-crash.patch | Yes, the pointer provided by the caller, coming from the RPC buffer, may not actually be safe to dereference. Try this with /run/shm as tmpfs with the crash server configured to dump cores: #include <fcntl.h> #include <sys/mman.h> #include <unistd.h> #include <stdio.h> #include <string.h> #define name "/run/shm/test.txt" int main(void) { int fd = open(name, O_RDWR|O_CREAT, 0777); if (ftruncate(fd, 4096)) perror("fruncate"); char *c = mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); if (c == MAP_FAILED) perror("mmap"); if (close(fd)) perror("close"); if (unlink(name)) perror("unlink"); memset(c, 0, 4096); if (munmap(c, 4096)) perror("munmap"); return 0; } It will make *ext2fs* crash, because - removing a file from tmpfs make its memory object go away, thus making *c unwritable (it's not the bug at stake, the program here is meant to crash) - the crash server uses vm_read to read the process memory to write the core. GNU Mach achieves it by playing with virtual memory. - the crash server uses vm_write to write this to the FS. GNU Mach passes the RPC data out of line by playing with virtual memory. - ext2fs eventually tries to copy from the RPC data, assumed to be safe, to the memory object, here backed by the pager. But the data is actually not safe. That probably needs to be fixed at the mig layer, to make sure incoming out-of-line data is accessible before handing it to the routine? =================================================================== |
no | ||||
| getty-noclear | commit 1580c9ff7740e4672aea7028a2bf06b9f5dc7b0c getty: Ignore --noclear passed by sysvinit since version 2.95-5 diff --git a/daemons/getty.c b/daemons/getty.c index a6b394c2d..121026f93 100644 |
Samuel Thibault <samuel.thibault@ens-lyon.org> | no | 2026-06-08 | ||
| fix-rootless-build.patch | fix rootless buildInstead of setting the owner and setuid bit during `make install` which requires (fake) root, only set it in debian/rules via chown u+s |
Fabian Grünbichler <debian@fabian.gruenbichler.email> | no | |||
| rumpdisk-no-hd | =================================================================== | no | ||||
| machdev_trivfs_server | For the existing netdde translator... =================================================================== |
no | ||||
| runsystem-race | no | |||||
| ext2fs-crash | no | |||||
| devdir | =================================================================== | no | ||||
| hurddir | =================================================================== | no | ||||
| local-64b-align | Avoid 64b typing error on RPC with 64b members in structures, while we migrate to the fixed 64b structure alignment. To be removed after people have migrated both gnumach libc+hurd rebuilt against fixed mig. =================================================================== |
no | ||||
| git-SO_TIMESTAMP | commit 1495073d15dc618b0b07f4cc2744db190d5488ce pfinet: implement rudimentary SO_TIMESTAMP support This patch adds support for UDP packet timestamping only when both SO_TIMESTAMP and SCM_TIMESTAMP are defined. * pfinet/linux-src/include/net/sock.h: add timestamp flag * pfinet/linux-src/net/core/sock.c: modify sock_*sockopt to set and query the timestamp flag. * pfinet/linux-src/net/ipv4/udp.c: call put_cmsg in udp_recvmsg to write the packet timestamp to the message anciliary data. Message-ID: <20260531183430.1305-1-dnietoc@gmail.com> diff --git a/pfinet/linux-src/include/net/sock.h b/pfinet/linux-src/include/net/sock.h index 5c4444d1a..435f8870d 100644 |
Diego Nieto Cid <dnietoc@gmail.com> | no | 2026-05-31 | ||
| git-autologin | commit 33550688ed21381c00a46c85f12c2e0bc0c9091f getty: Add -a (autologin) support diff --git a/daemons/getty.c b/daemons/getty.c index 121026f93..472f04779 100644 |
Samuel Thibault <samuel.thibault@ens-lyon.org> | no | 2026-06-08 | ||
| rumpuser-mem32 | [PATCH 2/2 Hurd] Use memory with 32 bit physical addresses where potentially required. Some rumpkernel APIs require memory allocated from 32 bit space if the underlying device requires it for DMA. It is not clear which devices require this so use it for all disk devices for the time being. |
Mike Kelly <mike@weatherwax.co.uk> | no | |||
| git-ext2fs-journal-lock | commit d80222b97855fc3ffe9f7c1856cfd3740b5788dc ext2fs: Fix journal deadlock during transaction finalization When a VFS thread finalizes a transaction in journal_stop_transaction_locked, it holds the global j_state_lock while performing memcpy to hydrate shadow buffers from the live Mach virtual memory cache (bptr). Under heavy memory pressure, this memcpy can trigger a Page Fault. If the Mach kernel decides to evict dirty pages to satisfy the fault, the ext2fs pager is invoked. The pager then attempts to write blocks to disk, which requires acquiring the j_state_lock but that lock is already held by the suspended VFS thread, causing a circular deadlock. Fix: Decouple memory hydration (memcpy) from the j_state_lock. - While holding the lock, identify blocks needing hydration and stage them in a thread-local list using jb_next. - Temporarily increment t_updates to protect the transaction from being freed. - Drop the j_state_lock to perform the memcpy. If a page fault occurs here, the pager can now safely acquire the lock to satisfy the I/O. - Re-acquire the lock and decrement t_updates to finalize the commit. This ensures the lock is never held while accessing pageable memory. Test: I have run the scenario in which i can recreate the deadlock multiple times with debugging messages on and off, and i don't manage to cause this specific deadlock scenario any more. diff --git a/ext2fs/journal.c b/ext2fs/journal.c index c50c742f8..99268cf75 100644 |
Milos Nikic <nikic.milos@gmail.com> | no | 2026-06-26 |
All known versions for source package 'hurd'
- 1:0.9.git20260527-3 (sid)