linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nadav Amit <namit@vmware.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
	"Michael Kerrisk )" <mtk.manpages@gmail.com>,
	Peter Xu <peterx@redhat.com>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH 2/2] userfaultfd.2: fix userfaultfd_demo output
Date: Mon, 10 Apr 2023 19:57:11 +0000	[thread overview]
Message-ID: <2C89D6DA-8B73-493F-95D7-456507D00EEE@vmware.com> (raw)
In-Reply-To: <5bce07b9-d4b7-8cb4-273d-72c3867682ba@gmail.com>


> On Apr 8, 2023, at 6:34 AM, Alejandro Colomar <alx.manpages@gmail.com> wrote:
> 
> Hi Nadav,
> 
> On 3/7/22 19:48, Nadav Amit wrote:
>> From: Nadav Amit <namit@vmware.com>
>> 
>> A bug in the kernel caused in recent version a different output (masked
>> offset). Update the output of the demo program accordingly.
> 
> I'd like to have some more information about this in the commit message.
> I don't really understand it.  When was the bug introduced?  When was it
> fixed?  Was the example in the page created in a buggy version?

Hi Alex,

Sorry for the late response.

The bug was introduced in 1a29d85eb0f1 ("mm: use vmf->address instead of of
vmf->virtual_address”) which is circa 2016. It was introduced shortly after
userfaultfd, so it was determined that no users are likely to rely on the
intended correct behavior that was documented in the man page, but there
might be users who relied on the wrong behavior, which was in the code
for several years.

More information is available in the patch of the fix:

https://lore.kernel.org/all/20220226022655.350562-1-namit@vmware.com/

Let me know if it answers you questions, and whether you want me to send
an updated patch for the man page.


  reply	other threads:[~2023-04-10 19:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 18:48 [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_EXACT_ADDRESS Nadav Amit
2022-03-07 18:48 ` [PATCH 2/2] userfaultfd.2: fix userfaultfd_demo output Nadav Amit
2022-03-14 12:28   ` Alejandro Colomar (man-pages)
2023-04-08 13:34   ` Alejandro Colomar
2023-04-10 19:57     ` Nadav Amit [this message]
2023-06-02  0:18       ` Alejandro Colomar
2022-03-14 12:23 ` [PATCH 1/2] ioctl_userfaultfd.2: add UFFD_FEATURE_EXACT_ADDRESS Alejandro Colomar (man-pages)
2023-03-30 22:52   ` Alejandro Colomar
2023-04-04 16:01     ` Nadav Amit
2023-04-08 13:32       ` Alejandro Colomar

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=2C89D6DA-8B73-493F-95D7-456507D00EEE@vmware.com \
    --to=namit@vmware.com \
    --cc=alx.manpages@gmail.com \
    --cc=david@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=peterx@redhat.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).