From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Davide Giorgio <davide@giorgiodavide.it>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: pivot_root - wrong check on mount(2)
Date: Fri, 27 Nov 2020 09:45:52 +0100 [thread overview]
Message-ID: <c3230381-a3d1-a655-ca05-e14a23971740@gmail.com> (raw)
In-Reply-To: <b5ecab54-f558-079a-9a4b-b2d6b500d54c@gmail.com>
On 11/27/20 9:30 AM, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
>
> On 11/26/20 1:28 PM, Alejandro Colomar (mailing lists; readonly) wrote:
>>
>>
>> On 11/26/20 10:31 AM, Michael Kerrisk (man-pages) wrote:
>>> Hello Davide,
>>>
>>> On Thu, 26 Nov 2020 at 01:01, Davide Giorgio <davide@giorgiodavide.it> wrote:
>>>>
>>>> Good morning,
>>>>
>>>> reading the pivot_root man page
>>>> (https://man7.org/linux/man-pages/man2/pivot_root.2.html)
>>>> there seems to be an error in the example source program
>>>> "pivot_root_demo.c".
>>>> In particular, there is a wrong check on the return value of mount(2).
>>>> https://man7.org/linux/man-pages/man2/mount.2.html#RETURN_VALUE
>>>>
>>>> The error is in this line
>>>> if (mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, NULL) == 1)
>>>>
>>>> that should be
>>>> if (mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, NULL) == -1)
>>>>
>>>>
>>>> Thank you for your work, kind regards
>>>
>>> Thanks! Fixed!
>>
>> Hi Michael,
>>
>> What about fixing this from a different approach:
>>
>> instead of comparing against -1
>> for functions that either return either 0 or -1,
>> we can include those functions in the greater family of
>> functions that return either 0 or non-zero (error code).
>> I propose comparing against 0:
>>
>> - if (mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, NULL) == 1)
>> + if (mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, NULL) != 0)
>>
>> I consider this to be safer, simpler,
>> and although negligible, also faster.
>>
>> What are your thoughts?
>
> History and the standards say -1. (Okay, mount(2) is not in
> POSIX, but the statement is true for syscalls generally.) So, I
> prefer to use -1 (and always do so in my own code.)
>
> The check "ret != 0" does not work for system calls that
> return a nonnegative value on success (e.g., open()).
>
> The check "ret < 0" does not work for system calls that
> can legitimately return a value less than zero on success.
> (getpriority() is the most notable example, but there
> are one or two other cases also.)
>
> The check "ret == -1" is clear, and--in a standards
> sense--precise. Though one must still be careful, since,
> for example, getpriority() can return -1 on success.
> (See the manual page for info on how to fdeal with this.)
Hi Michael,
Hmmm, I understand.
Thanks,
Alex
>
> Thanks,
>
> Michael
>
prev parent reply other threads:[~2020-11-27 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 0:01 pivot_root - wrong check on mount(2) Davide Giorgio
2020-11-26 9:31 ` Michael Kerrisk (man-pages)
2020-11-26 12:28 ` Alejandro Colomar (mailing lists; readonly)
2020-11-26 13:40 ` Alejandro Colomar (man-pages)
2020-11-27 8:30 ` Michael Kerrisk (man-pages)
2020-11-27 8:45 ` Alejandro Colomar (man-pages) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3230381-a3d1-a655-ca05-e14a23971740@gmail.com \
--to=alx.manpages@gmail.com \
--cc=davide@giorgiodavide.it \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).