<div dir="ltr">While you are it, shouldn't pr_msg() calls when reporting an error be replaced with pr_err()? We have a mix of these calls which doesn't look right to me. For example:<div><br></div><div>pr_err("fdinfo doesn't contain the mnt_id field\n");</div><div>pr_msg("/proc/<pid>/timers file is missing.\n");</div><div><br></div><div>--Saied</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 14, 2016 at 1:56 AM, Cyrill Gorcunov <span dir="ltr"><<a href="mailto:gorcunov@gmail.com" target="_blank">gorcunov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Mar 14, 2016 at 11:31:02AM +0300, Pavel Emelyanov wrote:<br>
> When the PR_SET_MM_MAP_SIZE is not supported (kernels prior to 3.17)<br>
> we try to check for older API, but there's a set of bugs in there.<br>
><br>
> This set fixes them all (I hope).<br>
</div></div>Acked-by: Cyrill Gorcunov <<a href="mailto:gorcunov@openvz.org">gorcunov@openvz.org</a>><br>
<br>
Thank you!<br>
</blockquote></div><br></div>