From: stsp <stsp2@yandex.ru>
To: Peter Xu <peterx@redhat.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Mike Rapoport <rppt@kernel.org>
Subject: Re: userfaultfd: two-step UFFDIO_API always gives -EINVAL
Date: Mon, 25 Nov 2024 20:07:34 +0300 [thread overview]
Message-ID: <da978e8c-2a72-4b7b-ae67-41e6ff0d5089@yandex.ru> (raw)
In-Reply-To: <Z0Ssq15MQd3rimBr@x1n>
25.11.2024 19:58, Peter Xu пишет:
> On Mon, Nov 25, 2024 at 07:15:10PM +0300, stsp wrote:
>> Man page clearly talks about
>> "the userfaultfd object" (one object)
>> when mandating the "two-step handshake".
>> I spent hours of head-scratching
>> before went looking into the sources,
>> and even then I was confident the man
>> page is right: people should always assume
>> documentation is correct, code is buggy.
> Hmm yes. I didn't pay much attention initially, but then after I read the
> latest man-pages/, especially "UFFDIO_API(2const)" I found it looks indeed
> wrong in the doc.
>
> In this case we can't change the code because we need to keep it working
> like before to not break ABI. We may still update the doc.
I wonder if some non-ABI-breaker
is possible, like eg keep the current
behavior of "features=0", but allow
to (optionally) override that by a
non-0 request? Yes, I've seen kselftests
are trying to double-register after 0,
but IIRC they tried to register wrong
options, which would fail anyway.
next prev parent reply other threads:[~2024-11-25 17:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 15:13 stsp
2024-11-25 9:05 ` stsp
2024-11-25 15:59 ` Peter Xu
2024-11-25 16:15 ` stsp
2024-11-25 16:58 ` Peter Xu
2024-11-25 17:07 ` stsp [this message]
2024-11-25 17:13 ` Peter Xu
2024-11-25 17:32 ` stsp
2024-11-25 17:44 ` Peter Xu
2024-11-25 18:01 ` stsp
2024-11-25 18:44 ` Muhammad Usama Anjum
2024-11-26 7:32 ` stsp
2024-11-26 15:56 ` Peter Xu
2024-11-26 16:16 ` stsp
2024-11-26 17:41 ` Peter Xu
2024-11-26 9:41 ` stsp
2024-11-25 22:42 ` Axel Rasmussen
2024-11-26 7:39 ` stsp
2024-11-26 15:50 ` Peter Xu
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=da978e8c-2a72-4b7b-ae67-41e6ff0d5089@yandex.ru \
--to=stsp2@yandex.ru \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=usama.anjum@collabora.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
all inboxes | Powered by JetHome®