@aktau `xrealloc` may generate less syscalls than a `free/malloc` pair and has the potential to be more optimized as it has control of the whole operation. It's hard to say which one is faster. @harsh1kumar Let's leave it as it is (free + xmalloc) as `xrealloc` sematics are different -- adjust the size of this buffer "keeping" its original content there -- and we don't care about original `confirm_msg` content here.

@harsh1kumar `alloc` #632 and `lalloc` #665 should be gone soon. @watk said he would start removing the remaining `alloc` calls to continue what was started in #632.