https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-9293 Lustre <p>the ocd_ibits_known field contains supported MDS inodebits from the client/server and maintained properly on both sides but not used anywhere. The only case is mdc_lock_match() where it is checked to exclude bits not supported on server.<br/> Meanwhile the LOV sets ocd_ibits_known to MDS_INODEBITS_UPDATE only, but MDT-MDT locks can be LOOKUP and XATTR at the same time and everything works just fine.<br/> That makes no sense so cleanup is needed in this area to use ocd_ibits_known properly and check it against enqueued locks.</p> LU-9293

ocd_ibits_known is not checked

Bug Minor Closed Fixed Mikhail Pershin Mikhail Pershin Wed, 5 Apr 2017 09:35:54 +0000 Sun, 16 Jan 2022 08:20:55 +0000 Sun, 16 Jan 2022 08:20:55 +0000 0 3 <p>I also see <tt>ocd_ibits_known</tt> being checked in <tt>client_common_fill_super()</tt> and <tt>mdc_xattr_common()</tt> to enable the xattr cache (<tt>MDS_INODELOCK_XATTR</tt>). The only other new ibits types are:</p> <ul class="alternate" type="square"> <li><tt>MDS_INODELOCK_LAYOUT</tt> but the "interoperability" of that flag has already passed (I don't recall exact details) so all clients and servers are assumed to have this support.</li> <li><tt>MDS_INODELOCK_PERM</tt> is masked on the client by <tt>mdc_lock_match()</tt> so I don't think there needs to be a compatibility check. Older servers and clients don't require this since it is only for DNE.</li> </ul> <p>Mike, is this still an issue?</p> Related LU-10175 Development Rank 1|hzz9bz: Rank (Obsolete) 9223372036854775807 Severity