summaryrefslogtreecommitdiff
path: root/block
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2021-03-12 15:07:09 -0600
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-03-17 17:06:27 +0100
commit5d5422a294e6c0756993288ec372ed445a2ccdfe (patch)
tree9f8aae2fa8925cc8b492314f7c2a59379b9b7dc8 /block
parent29bc89c8b48dd1bfd7b1f55143b5d75d599e2a12 (diff)
Revert 95ebabde382c ("capabilities: Don't allow writing ambiguous v3 file capabilities")
commit 3b0c2d3eaa83da259d7726192cf55a137769012f upstream. It turns out that there are in fact userspace implementations that care and this recent change caused a regression. https://github.com/containers/buildah/issues/3071 As the motivation for the original change was future development, and the impact is existing real world code just revert this change and allow the ambiguity in v3 file caps. Cc: stable@vger.kernel.org Fixes: 95ebabde382c ("capabilities: Don't allow writing ambiguous v3 file capabilities") Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions