Dangling/orphaned shared library as MAP_DENYWRITE result ( BUG)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello list,
 
I applied MAP_DENYWRITE flag to shared object ( kernel 4.8)
 
I compiled test shared library and small executable who uses it.
 
Then executable which used it works as expected,
 
and any attempt to change shared library rejected with EXTBUSY error.
 
But when executable terminated, library is still busy.
 
I though that kernel will clean inode counters, if nobody else reference it
(and this is my case - I am the only user of this lib)
 
Is this behaviour a BUG , I mean reference count is zero, but kernel not zeroed i_writecount ?)
 
I suppose that the memory is unmapped, but how can I confirm it ? ( do not have pid for pmap )
 
Regars,
Lev
 
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux