Bug 13983 - mtime updated on Solaris when accessing extended attributes
Summary: mtime updated on Solaris when accessing extended attributes
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.9.8
Hardware: All Solaris
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-01 21:53 UTC by Björn Jacke
Modified: 2019-06-03 12:00 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Jacke 2019-06-01 21:53:28 UTC 
On Solaris 10, when only openat() is called (for accessing EA data) on a file this updates the mtime of the file to the current time even if no extended attribute is being read or written. This is definetely a (not very well known) Solaris bug.

Solaris 11 is less broken in the respect, here an openat() call does not update the mtime but the mtime of the file *is* being updated when an extended attribute is being written. For the way EAs are implmented in Solaris this might the intended behaviour though.

mtime updates when EAs are modified are not desired by Samba though. We might consider to save and reset the mtime on EA changes. Thoughts ?
Comment 1 Björn Jacke 2019-06-03 12:00:16 UTC 
small correction: modification of EAs does not update the mtime on Solaris, don't know why I had in mind that it would.

On the Solaris 11 machines I had access to there where also pre-existing EAs, maybe just for that reason the mtime update issues do not pop up there and would pop up if there were files without any pre-existing EAs.