Summary: | sys-boot/grub-2.04-r1: USE="libzfs" causes sandbox violation in /etc/exports.d | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jacob Godserv <jacobgodserv> |
Component: | Current packages | Assignee: | Richard Yao (RETIRED) <ryao> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | base-system, gyakovlev, jstein, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | tail-build.log.txt |
Description
Jacob Godserv
2020-09-14 15:03:07 UTC
Created attachment 660138 [details]
tail-build.log.txt
Here's the end of the build.log where the error happens.
Adding /etc/exports.d to the allowed sandbox list obviously allowed this to work, but I neither had a prior /etc/exports.d, nor did the merge create one. Very odd. It's quite possible that ZFS itself is trying to do this: https://github.com/openzfs/zfs/issues/10785 Seems like an issue that should be addressed in libzfs. I guess zfs version is 2.0.0-rc1? there's a PR fixing it https://github.com/openzfs/zfs/pull/10934 I can add it after it's reviewed/merged. workaround is simple enough, just creating /etc/exports.d we could add addpredict to grub, but it's not the correct solution. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c10c708ba999cd9aa08aae373d4103522ad7d358 commit c10c708ba999cd9aa08aae373d4103522ad7d358 Author: Georgy Yakovlev <gyakovlev@gentoo.org> AuthorDate: 2020-09-25 20:24:26 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2020-09-25 20:28:20 +0000 sys-fs/zfs: add exports.d patch Closes: https://bugs.gentoo.org/742503 Package-Manager: Portage-3.0.8, Repoman-3.0.1 Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> .../files/2.0.0_rc2-exports-d-permissions.patch | 189 +++++++++++++++++++++ ...fs-2.0.0_rc2.ebuild => zfs-2.0.0_rc2-r1.ebuild} | 5 +- 2 files changed, 193 insertions(+), 1 deletion(-) |