Comment 4 for bug 1915095

Hi Brandon and Sergio,

Can you guys still reproduce this? I ran the steps Sergio outlined but didn't see the atime change:

triage-kinetic+22.10:~$ sudo apt install clamav
...
The following packages will be upgraded:
  clamav
1 upgraded, 0 newly installed, 0 to remove and 199 not upgraded.
Need to get 130 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu kinetic/main amd64 clamav amd64 0.103.6+dfsg-1ubuntu1 [130 kB]
Fetched 130 kB in 1s (167 kB/s)
(Reading database ... 71567 files and directories currently installed.)
Preparing to unpack .../clamav_0.103.6+dfsg-1ubuntu1_amd64.deb ...
Unpacking clamav (0.103.6+dfsg-1ubuntu1) over (0.103.6+dfsg-1ubuntu1) ...
Setting up clamav (0.103.6+dfsg-1ubuntu1) ...
Processing triggers for man-db (2.10.2-1) ...
triage-kinetic+22.10:~$ echo hi > test
triage-kinetic+22.10:~$ stat test
  File: test
  Size: 3 Blocks: 8 IO Block: 4096 regular file
Device: fd08h/64776d Inode: 274348 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1000/ bryce) Gid: ( 1000/ bryce)
Access: 2022-06-07 15:49:13.832795785 +0000
Modify: 2022-06-07 15:49:13.832795785 +0000
Change: 2022-06-07 15:49:13.832795785 +0000
 Birth: 2022-06-07 15:49:13.832795785 +0000
triage-kinetic+22.10:~$ stat test | grep Access:
Access: (0664/-rw-rw-r--) Uid: ( 1000/ bryce) Gid: ( 1000/ bryce)
Access: 2022-06-07 15:49:13.832795785 +0000
triage-kinetic+22.10:~$ clamscan test
/home/bryce/test: OK

----------- SCAN SUMMARY -----------
Known viruses: 8617627
Engine version: 0.103.6
Scanned directories: 0
Scanned files: 1
Infected files: 0
Data scanned: 0.00 MB
Data read: 0.00 MB (ratio 0.00:1)
Time: 19.603 sec (0 m 19 s)
Start Date: 2022:06:07 15:49:56
End Date: 2022:06:07 15:50:16
triage-kinetic+22.10:~$ stat test
  File: test
  Size: 3 Blocks: 8 IO Block: 4096 regular file
Device: fd08h/64776d Inode: 274348 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1000/ bryce) Gid: ( 1000/ bryce)
Access: 2022-06-07 15:49:13.832795785 +0000
Modify: 2022-06-07 15:49:13.832795785 +0000
Change: 2022-06-07 15:49:13.832795785 +0000
 Birth: 2022-06-07 15:49:13.832795785 +0000

I also tested on jammy and focal, which have already had the same clamav version backported, and similarly did not reproduce.

The upstream bug report is still open, and there are no mentions of atime fixes in the clamav changelog upstream, but I tested older versions of clamav - 0.103.5+dfsg-1 on jammy, and 0.102.2+dfsg-2ubuntu1 on focal, but also with those after running clamscan the Access, Birth and Modify times are identical and unchanged. Could this have been fixed elsewhere than clamav, or could there be some system settings necessary to reproduce?

Do you recall what clamav version you tested this on originally? Or what ubuntu release was used? Are you still able to reproduce the faulty behavior?