diff options
| author | Warner Losh <imp@FreeBSD.org> | 2026-10-03 14:42:58 +0000 |
|---|---|---|
| committer | Warner Losh <imp@FreeBSD.org> | 2026-10-03 17:32:08 +0000 |
| commit | 262fa4695d90207b9080f2cc5cb01eccf07fe243 (patch) | |
| tree | a5665bbef50c6ac7bb1d34aaf1db8d1b62b1b782 /lldb/source/Plugins/Process/gdb-remote/(public-mirror) | |
| parent | f382ef1dc82cf0679b164be1e6cce51c022a204c (diff) | |
Get the link offset using the zfs_dnode_sa_lookup helper now.
Recently, the symbolic links we rely on in the boot loader have stopped
working.
Prior to OpenZFS commit e90badec11d3 ("Inherit the project ID for every
object type", Matt Turner, 2026-08-14), symbolic link information was
written at a fixed offset in the SA data. Since that commit, the
inherited PROJIDs mean that all pools with quota enabled have started
writing symbolic links with a new, non-fixed offset. Old symbolic links
remained unchanged, but new ones were written with a different
offset. At work, we have all these things: rewritten BEs, quotas, and a
dependence on symbolic links in our boot path.
This came in on 2026-08-24 OpenZFS merge (22649d4dba73). This was 12
hours after stab week for August, so we didn't hit this until the
September stab week. Since the new kernel has to write links at the new
offset, the initial tests worked, but the second ones didn't.
Sponsored by: Netflix
Differential Revision: https://reviews.freebsd.org/D60268
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/(public-mirror)')
0 files changed, 0 insertions, 0 deletions
