- User Since
- May 16 2014, 7:35 PM (265 w, 3 d)
Sun, Jun 16
Feel free to do the rename in the preliminary commit.
Sat, Jun 15
Fri, Jun 14
Thu, Jun 13
Wed, Jun 12
Tue, Jun 11
So you relock range for each chunk ? This defeats the purpose of the range locking. Should copy_file_range() be atomic WRT other reads and writes ?
Is this a fix for the i386 wrap issue, or just a related change ?
Mon, Jun 10
I believe that you should allocate a flag in the feature note and use it to opt-out (or opt-in ?) of max_prot.
Sun, Jun 9
Sat, Jun 8
Fri, Jun 7
Thu, Jun 6
I think this version of code is technically correct. I still would prefer the fd-based sysctl instead.
Wed, Jun 5
Tue, Jun 4
I suspect it could be more useful to pass a file descriptor number to the sysctl, leaving path manipulation to open. E.g., this way it would be possible to hack-reclaim unlinked inodes.
Mon, Jun 3
Sun, Jun 2
Sat, Jun 1
Could you please update the diff to include the definition if vm_page_wired() ? I expect it to be trivial.
Imagine that there is no pseudo ttys in the system, and user called mkdir('/dev/pts'). Then a new pty pair is created, which makes a device node in /dev/pts. On device destruction, the node is removed, and its contained directory is removed if empty. But '/dev/pts' was created by user, not my makedev(9).
Your follow-up questions definitely show that you want some mountd.conf config file, e.g. to manage -I flag. The file should be re-read on SIGHUP.
I could argue that it is reasonable for mountd.conf to provide all options supplied as command-line arguments to mountd.