<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in sys</title>
    <link>http://nxr.netbsd.org/rss/src/external/cddl/osnet/dist/uts/common/fs/zfs/sys/</link>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2005</copyright>
    <generator>Java</generator>
    
<item>
    <title>zfs: port a fix for data corruption issue from illumos<br/><br/>see https://www.illumos.org/issues/17734 for the details.<br/><br/>note: i didn't bother to patch illumos/freebsd code in our tree.<br/><br/>the original commit message:<br/><br/>&gt; commit f6559a18843abdfa5849b9e74f239f9bd15796d3<br/>&gt; Author: Andy Fiddaman &lt;illumos@fiddaman.net&gt;<br/>&gt; Date:   Mon Nov 10 22:52:05 2025 +0000<br/>&gt;<br/>&gt;     17734 ZFS fsync can trigger ZIL transaction reordering and data corruption<br/>&gt;     Portions contributed by: Alexander Motin &lt;mav@FreeBSD.org&gt;<br/>&gt;     Reviewed by: Ryan Zezeski &lt;ryan@zinascii.com&gt;<br/>&gt;     Reviewed by: Toomas Soome &lt;tsoome@me.com&gt;<br/>&gt;     Approved by: Dan McDonald &lt;danmcd@edgecast.io&gt;<br/><br/>a review request on tech-kern:<br/>https://mail-index.netbsd.org/tech-kern/2026/03/04/msg030862.html</title>
    <description></description>
    <pubDate>Fri Mar 27 14:00:00 UTC 2026</pubDate>
    <dc:creator>yamt</dc:creator>
</item>

<item>
    <title>zfs: add zfs_range_lock_try<br/><br/>i plan to use this to fix pgdaemon deadlock issue. (PR/60004)<br/>(thus i didn't bother to implement RL_READER.)<br/><br/>note: recent openzfs has a similar function. (zfs_rangelock_tryenter)<br/>this commit ought to be reverted when/if we switch to it.<br/><br/>https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=60004</title>
    <description></description>
    <pubDate>Fri Feb 20 08:00:00 UTC 2026</pubDate>
    <dc:creator>yamt</dc:creator>
</item>

<item>
    <title>zfs: Expose hostid to zfs, as in gethostid/sethostid(3).<br/><br/>If set to nonzero, the hostid is recorded in the metadata of a zpool,<br/>and checked by `zpool import' when the pool has not been explicitly<br/>exported.  After reboot, zpool import will not need `-f' to reimport<br/>the pool.<br/><br/>Setting the hostid must be done explicitly through sysctl (or the<br/>sethostid(3) library call) on all ports except acorn32, amiga,<br/>mvme68k, newsmips, sparc, sparc64, sun2, and sun3.  So for most users<br/>this change will have no immediate effect.  But you can obviate the<br/>need for `zpool import -f' by adding `kern.hostid=123456789' to<br/>/etc/sysctl.conf and importing the pool one last time with `-f'.</title>
    <description></description>
    <pubDate>Tue Dec 28 17:00:00 UTC 2021</pubDate>
    <dc:creator>riastradh</dc:creator>
</item>

<item>
    <title>Change dmu_diff() back to use a "file" instead of a "vnode".<br/>Command "zfs diff" calls it with a pipe, not a plain file.<br/><br/>Fixes PR kern/54541: kernel panic using "zfs diff"</title>
    <description></description>
    <pubDate>Mon Oct 14 13:00:00 UTC 2019</pubDate>
    <dc:creator>hannken</dc:creator>
</item>

<item>
    <title>Try to retrieve the per-disk maximum transfer size and use it instead<br/>of MAXPHYS.  Eagerly waiting for the merge of tls-maxphys.<br/><br/>Addresses PR port-xen/54273: "zpool create pool xbd2" panics DOMU kernel</title>
    <description></description>
    <pubDate>Tue Jun 11 09:00:00 UTC 2019</pubDate>
    <dc:creator>hannken</dc:creator>
</item>

<item>
    <title>Enable the zvol minor management to create and remove device nodes.</title>
    <description></description>
    <pubDate>Wed May 22 08:00:00 UTC 2019</pubDate>
    <dc:creator>hannken</dc:creator>
</item>

<item>
    <title>Make ZFS exportable by NFS, implement zfsctl_vptofh(),<br/>zfs_netbsd_vptofh() and zfs_netbsd_fhtovp().<br/><br/>Undo changes to now completely unused zfs_fhtovp().</title>
    <description></description>
    <pubDate>Mon Mar 18 09:00:00 UTC 2019</pubDate>
    <dc:creator>hannken</dc:creator>
</item>

<item>
    <title>Be consistent about _KERNEL vs _HARDKERNEL in zfs.<br/><br/>As it happens, on x86 both _HARDKERNEL and _KERNEL get defined; see<br/>the conditional in sys/rump/Makefile.rump that _refrains_ from<br/>defining _RUMPKERNEL on x86.<br/><br/>So the only version of this code that has been tested is the one with<br/>all of it included.  But on, e.g., aarch64, we do not get _HARDKERNEL<br/>here, and the code fails to build because some things use the field<br/>struct spa::spa_deadman_cycid under _KERNEL when it is declared only<br/>under _HARDKERNEL.<br/><br/>If there's a reason _not_ to use this in rump -- and it's not obvious<br/>to me why -- then all access to the field needs to agree to use<br/>_HARDKERNEL.</title>
    <description></description>
    <pubDate>Thu Nov 15 04:00:00 UTC 2018</pubDate>
    <dc:creator>riastradh</dc:creator>
</item>

<item>
    <title>merge a new version of the CDDL dtrace and ZFS code.<br/>this changes the upstream vendor from OpenSolaris to FreeBSD,<br/>and this version is based on FreeBSD svn r315983.<br/><br/>in addition to the 10 years of improvements from upstream,<br/>this version also has these NetBSD-specific enhancements:<br/> - dtrace FBT probes can now be placed in kernel modules.<br/> - ZFS now supports mmap().</title>
    <description></description>
    <pubDate>Mon May 28 21:00:00 UTC 2018</pubDate>
    <dc:creator>chs</dc:creator>
</item>

<item>
    <title>branches:  1.1.1;<br/>Initial revision</title>
    <description></description>
    <pubDate>Fri Aug 07 18:00:00 UTC 2009</pubDate>
    <dc:creator>haad</dc:creator>
</item>

<item>
    <title>branches:  1.1.1;<br/>Initial revision</title>
    <description></description>
    <pubDate>Mon May 28 20:00:00 UTC 2018</pubDate>
    <dc:creator>chs</dc:creator>
</item>
</channel></rss>

