zfs posix default permissions lost on reboot or unmount
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Colin Ian King | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Colin Ian King |
Bug Description
[SRU Justification]
Commit 4967a3e introduced a typo that caused the ZPL to store the
intended default ACL as an access ACL. Due to caching this problem
may not become visible until the filesystem is remounted or the inode
is evicted from the cache.
[FIX]
https:/
[TESTCASE]
from https:/
[root@localhost ~]# cd /mnt/data/
[root@localhost data]# mkdir test_dir
[root@localhost data]# setfacl -R --mask -m u:uadm:rwX test_dir/
[root@localhost data]# setfacl -R -d --mask -m u:uadm:rwX test_dir/
[root@localhost data]# getfacl test_dir/
# file: test_dir/
# owner: root
# group: root
user::rwx
user:uadm:rwx
group::r-x
mask::rwx
other::r-x
default:user::rwx
default:
default:group::r-x
default:mask::rwx
default:other::r-x
[root@localhost data]# reboot
After a reboot without the fix one gets the following ACLs:
[root@localhost ~]# cd /mnt/data/
[root@localhost data]# getfacl test_dir/
# file: test_dir/
# owner: root
# group: root
user::rwx
user:uadm:rwx
group::r-x
mask::rwx
other::r-x
With the fix:
[root@localhost data]# getfacl test_dir/
# file: test_dir/
# owner: root
# group: root
user::rwx
user:uadm:rwx
group::r-x
mask::rwx
other::r-x
default:user::rwx
default:
default:group::r-x
default:mask::rwx
default:other::r-x
[REGRESSION POTENTAL]
Minimal ZFS only and touches just acl setting. This corrects just the ACL_TYPE_DEFAULT case for the ACL setting for ZFS, and sets it to the *correct* name. It is a trivial one line fix.
-------
Ubuntu 16.04 server
Problem: Posix default permissions on zfs datasets are lost after rebooting the server or unmounting/remount.
See here for details and fix: https:/
---
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Apr 24 22:44 seq
crw-rw----+ 1 root audio 116, 33 Apr 24 22:44 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=
IwConfig: Error: [Errno 2] No such file or directory
MachineType: To be filled by O.E.M. To be filled by O.E.M.
NonfreeKernelMo
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 nouveaufb
1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.157
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/23/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6702
dmi.board.
dmi.board.name: P8B-X series
dmi.board.vendor: ASUSTeK Computer INC.
dmi.chassis.
dmi.chassis.type: 17
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To be filled by O.E.M.
dmi.product.
dmi.sys.vendor: To be filled by O.E.M.
CVE References
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Confirmed → In Progress |
importance: | Undecided → High |
assignee: | nobody → Colin Ian King (colin-king) |
description: | updated |
Changed in linux (Ubuntu Xenial): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Yakkety): | |
status: | In Progress → Fix Released |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1574801/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]