RE: [RFC PATCH 0/5] madvise MADV_DOEXEC

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

 



> Maybe.  We still need to preserve an anonymous segment, though.  MADV_DOEXEC, or mshare,
> or something else.  And I think the ability to preserve memory containing pointers to itself
> is an interesting use case, though not ours.

Why does all this remind me of the old sendmail code.
After parsing the config file it used to write its entire data
area out to a file.
On restart, if the config file hadn't changed it would read it back it.

It sort of worked - until shared libraries came along.
Then it had a habit of generating random crashes.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux