© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Marking the glibc task as invalid (see IRC conversation)
<chrisccoulson> does the kernel in yakkety support MADV_FREE?
<apw> chrisccoulson, that is documented as 4.5+ so we will, and currently don't
<chrisccoulson> apw, ah thanks. See bug 1613258 for context - the new glibc defines MADV_FREE
<apw> chrisccoulson, that may have been built with the 4.6 which was in -proposed for a time (glibc)
<apw> that said, i am supprised that glibc is assuming it can use it
infinity, ^
<apw> chrisccoulson, oh but it is likely the seccomp bits right? so just a profile change ?
chrisccoulson, in the sense it is resonable for glibc to define it, and the kernel to return EINVAL or indeed work, but we need the seccomp profile to reflect that possibility
<chrisccoulson> apw, we'll probably end up doing the same as http://
<apw> chrisccoulson, wouldn't it make more sense to try MADV_FREE and if it fails ENOSUPPORT or whatever dropback to whatever it does when it doesn't have _FREE ?
<apw> so one uses it in 4.5 and not before that all shiney and automatically
<chrisccoulson> apw, we could probably do that