No system call when malloc after free












0















While I was playing a little with kernel audit system, I made a small C program:



#include <stdio.h>
#include <stdlib.h>

int main(int argc, char** argv){
void *t;
while(1){
t = malloc(1);
free(t);

}
return 0;
}


And applied the following filters to audit:



-a always,exit -F arch=b32 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b64 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b32 -S brk
-a always,exit -F arch=b64 -S brk


After compiling and running, I noticed that sys_brk wasn't showing up in the audit log.
Furthermore it didn't also appear in strace, even tho malloc was called (checked with ltrace).
Lastly I removed the free and the calls to sys_brk started showing up.



What is causing this type of behaviour? Does glibc make some kind of optimization in malloc and free functions to prevent useless syscalls?



TL;DR: free followed by malloc makes neither call the kernel. Why?










share|improve this question

























  • It might use brk () or mmap ()

    – 炸鱼薯条德里克
    1 hour ago













  • Neither appeared in strace

    – Jorge Heleno
    15 mins ago
















0















While I was playing a little with kernel audit system, I made a small C program:



#include <stdio.h>
#include <stdlib.h>

int main(int argc, char** argv){
void *t;
while(1){
t = malloc(1);
free(t);

}
return 0;
}


And applied the following filters to audit:



-a always,exit -F arch=b32 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b64 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b32 -S brk
-a always,exit -F arch=b64 -S brk


After compiling and running, I noticed that sys_brk wasn't showing up in the audit log.
Furthermore it didn't also appear in strace, even tho malloc was called (checked with ltrace).
Lastly I removed the free and the calls to sys_brk started showing up.



What is causing this type of behaviour? Does glibc make some kind of optimization in malloc and free functions to prevent useless syscalls?



TL;DR: free followed by malloc makes neither call the kernel. Why?










share|improve this question

























  • It might use brk () or mmap ()

    – 炸鱼薯条德里克
    1 hour ago













  • Neither appeared in strace

    – Jorge Heleno
    15 mins ago














0












0








0








While I was playing a little with kernel audit system, I made a small C program:



#include <stdio.h>
#include <stdlib.h>

int main(int argc, char** argv){
void *t;
while(1){
t = malloc(1);
free(t);

}
return 0;
}


And applied the following filters to audit:



-a always,exit -F arch=b32 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b64 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b32 -S brk
-a always,exit -F arch=b64 -S brk


After compiling and running, I noticed that sys_brk wasn't showing up in the audit log.
Furthermore it didn't also appear in strace, even tho malloc was called (checked with ltrace).
Lastly I removed the free and the calls to sys_brk started showing up.



What is causing this type of behaviour? Does glibc make some kind of optimization in malloc and free functions to prevent useless syscalls?



TL;DR: free followed by malloc makes neither call the kernel. Why?










share|improve this question
















While I was playing a little with kernel audit system, I made a small C program:



#include <stdio.h>
#include <stdlib.h>

int main(int argc, char** argv){
void *t;
while(1){
t = malloc(1);
free(t);

}
return 0;
}


And applied the following filters to audit:



-a always,exit -F arch=b32 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b64 -S open,openat -F exit=-EACCES -F key=access
-a always,exit -F arch=b32 -S brk
-a always,exit -F arch=b64 -S brk


After compiling and running, I noticed that sys_brk wasn't showing up in the audit log.
Furthermore it didn't also appear in strace, even tho malloc was called (checked with ltrace).
Lastly I removed the free and the calls to sys_brk started showing up.



What is causing this type of behaviour? Does glibc make some kind of optimization in malloc and free functions to prevent useless syscalls?



TL;DR: free followed by malloc makes neither call the kernel. Why?







linux linux-kernel linux-audit






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 56 mins ago









Rui F Ribeiro

41.2k1481139




41.2k1481139










asked 1 hour ago









Jorge HelenoJorge Heleno

1114




1114













  • It might use brk () or mmap ()

    – 炸鱼薯条德里克
    1 hour ago













  • Neither appeared in strace

    – Jorge Heleno
    15 mins ago



















  • It might use brk () or mmap ()

    – 炸鱼薯条德里克
    1 hour ago













  • Neither appeared in strace

    – Jorge Heleno
    15 mins ago

















It might use brk () or mmap ()

– 炸鱼薯条德里克
1 hour ago







It might use brk () or mmap ()

– 炸鱼薯条德里克
1 hour ago















Neither appeared in strace

– Jorge Heleno
15 mins ago





Neither appeared in strace

– Jorge Heleno
15 mins ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505038%2fno-system-call-when-malloc-after-free%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505038%2fno-system-call-when-malloc-after-free%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux