[LU-12657] sanity/103 and sanityn/25 fail with 4.18 kernel Created: 10/Aug/19  Updated: 01/Aug/23  Resolved: 21/Aug/19

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.13.0, Lustre 2.12.3

Type: Bug Priority: Minor
Reporter: Alex Zhuravlev Assignee: Alex Zhuravlev
Resolution: Fixed Votes: 0
Labels: arm, rhel8, sles12, ubuntu18, upstream

Issue Links:
Blocker
Related
is related to LU-10334 Ubuntu1604 client sanity-103a: FAIL: ... Resolved
is related to LU-12269 Support RHEL 8.0 Resolved
is related to LU-12511 Prepare lustre for adoption into the ... Open
is related to LU-11594 sanity test_103a: FAIL: permissions f... Resolved
is related to LU-13051 ACL fail on some clients or mount points Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

ACL revalidation doesn't work properly as ll_lock_cancel_bits() doesn't reset inode->i_acl and inode->i_default_acl to the initial state which is ACL_NOT_CACHED



 Comments   
Comment by Peter Jones [ 13/Aug/19 ]

https://review.whamcloud.com/#/c/35756/

Comment by Gerrit Updater [ 21/Aug/19 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/35756/
Subject: LU-12657 llite: forget cached ACLs properly
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 3df034f8f46b0d22829f7ac83cbf9871823c093c

Comment by Peter Jones [ 21/Aug/19 ]

Landed for 2.13

Comment by Gerrit Updater [ 22/Aug/19 ]

Minh Diep (mdiep@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/35870
Subject: LU-12657 llite: forget cached ACLs properly
Project: fs/lustre-release
Branch: b2_12
Current Patch Set: 1
Commit: 2a1f4ccdeb6623f1a605ea308ea64c1a4155acb4

Comment by Gerrit Updater [ 12/Sep/19 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/35870/
Subject: LU-12657 llite: forget cached ACLs properly
Project: fs/lustre-release
Branch: b2_12
Current Patch Set:
Commit: 5d0d4e6cc2f4effe8e49f59f85129b95c82c6987

Generated at Sat Feb 10 02:54:31 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.