Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 May 2021 19:53:18 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 256205] nullfs: data corruption with SEEK_HOLE/SEEK_DATA on dirty files
Message-ID:  <bug-256205-227-6L6tgVxybi@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-256205-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-256205-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256205

Alan Somers <asomers@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
            Version|13.0-STABLE                 |13.0-RELEASE
            Summary|lseek() with SEEK_HOLE some |nullfs: data corruption
                   |times wrongly reports holes |with SEEK_HOLE/SEEK_DATA on
                   |on ZFS                      |dirty files

--- Comment #20 from Alan Somers <asomers@FreeBSD.org> ---
I've confirmed that 42881526d401e7a9c09241e392b7ffa18cfe11d6 fixes the prob=
lem
on stable/13.  Now the question is whether secteam would accept this as an
errata and publish a fix for 13.0-RELEASE.  Data corruption is a pretty bad
problem, so I think they should.  I'll take it up with them.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256205-227-6L6tgVxybi>