Re: [PATCH 1/2] xattr support for ext2fs

LastAvengers writes: > +/* Prefixes are represented as numbers when stored in ext2 filesystems. */ > +struct _xattr_prefix > +xattr_prefixes[] = > +{ > + { > + 1, "user.", sizeof "user." - 1}, > + { > + 7, "gnu.", sizeof "gnu." - 1}, > + { > + 0, NULL, 0} > +}; ext4 on Linux 4.5 already us

[bug #48437] diskfs_S_file_set_translator shortcutting "/hurd/fifo" to S_IFIFO discards options

URL: Summary: diskfs_S_file_set_translator shortcutting "/hurd/fifo" to S_IFIFO discards options Project: The GNU Hurd Submitted by: kon Submitted on: Thu Jul 7 12:31:28 2016 Category

[bug #48438] Cannot replace /hurd/fifo with different passive translator

URL: Summary: Cannot replace /hurd/fifo with different passive translator Project: The GNU Hurd Submitted by: kon Submitted on: Thu Jul 7 12:38:01 2016 Category: Hurd Servers

[bug #48372] read with size 0 from fifo blocks

Follow-up Comment #5, bug #48372 (project hurd): I patched libpipe/pipe.c (pipe_recv) as described in comment #4, and the perl test case in the original submission no longer hangs. Neither does a similar test with /hurd/new-fifo. I also ran the test suite of vim-7.4.1829 with this patch and a fe

[bug #48371] read(fd, NULL, 0) from /dev/klog blocks until there is data

Follow-up Comment #3, bug #48371 (project hurd): I patched trans/streamio.c (trivfs_S_io_read) so that, if amount == 0, it returns success without blocking. I didn't change dev_read because it's called only from trivfs_S_io_read and I thought it'd be better to avoid locking global_lock in this ca

[bug #48371] read(fd, NULL, 0) from /dev/klog blocks until there is data

Update of bug #48371 (project hurd): Wiki-like text discussion box: => For such a two-lines patch, the changes are not copyrightable, so there is no need for a copyright assignment. ___ Reply to this item at:

[bug #48371] read(fd, NULL, 0) from /dev/klog blocks until there is data

Additional Item Attachment, bug #48371 (project hurd): File name: 0001-streamio-read-fd-buf-0-must-not-block.patch Size:1 KB ___ Reply to this item at: _

Re: [PATCH] i386: Omit pmap workaround on i486 or later.

How about this patch? Did I share this with you in a wrong way, or is it simply useless? 2016-06-18 22:04 GMT+09:00 Masanori Ogino : > As described in XXX comments, the workaround for memory mapping is > implemented for 80386 and it is unnecessary on i486 or later. Thus, it > is safe to omit that

RE: [PATCH 1/2] xattr support for ext2fs

> ext4 on Linux 4.5 already uses 7 for EXT4_XATTR_INDEX_SYSTEM > but lists it in neither ext4_xattr_handler_map nor > ext4_xattr_handlers. I think that means the index does not map > to any prefix visible to user mode, not even to > #define XATTR_SYSTEM_PREFIX "system.". Instead, ext4 uses > { EXT4

Re: [PATCH] i386: Omit pmap workaround on i486 or later.

Masanori Ogino, on Fri 08 Jul 2016 10:43:00 +0900, wrote: > Did I share this with you in a wrong way, or is it simply useless? Personnally, I simply currently have no time to spend on it :/ Samuel