From: David Hildenbrand <david@redhat.com>
To: Jerome Glisse <jglisse@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] mm: fix maxnode for mbind(), set_mempolicy() and migrate_pages()
Date: Wed, 24 Jul 2024 08:27:41 +0200 [thread overview]
Message-ID: <51bef112-67b5-48bb-a855-45ad25e05ecd@redhat.com> (raw)
In-Reply-To: <CAPTQFZS7KTTor+CHyzwE8hVVZo04haWsyTHhN9+Hy35PVZ6O1w@mail.gmail.com>
>> In any case, we have to document that behavior that existed since the
>> very beginning. Because it would be even *worse* if someone would
>> develop against a new kernel and would get a bunch of bug reports when
>> running on literally every old kernel out there :)
>>
>> So my best guess is that long-term it will create more issues when we
>> change the behavior ... but in any case we have to update the man pages.
>
> No it would not, if you had the fix and did not modify applications
> that are smart about it then nothing would change. Applications that
> are smart will work the same on both patched and unpatched kernels
> while applications that have the bug will suddenly have the behaviour
> they would have expected from the documentation.
See my other mail, this seems to be the expected behavior since the very
beginning.
So unless I am missing something important, the only thing to fix here
is the documentation.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-07-24 6:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 17:35 Jerome Glisse
2024-07-20 17:55 ` Matthew Wilcox
2024-07-22 21:21 ` Gregory Price
[not found] ` <0c390494-e6ba-4cde-aace-cd726f2409a1@redhat.com>
2024-07-23 16:19 ` Jerome Glisse
2024-07-23 16:33 ` Jerome Glisse
2024-07-23 17:37 ` David Hildenbrand
2024-07-23 18:24 ` David Hildenbrand
2024-07-24 4:15 ` Jerome Glisse
2024-07-24 6:27 ` David Hildenbrand [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=51bef112-67b5-48bb-a855-45ad25e05ecd@redhat.com \
--to=david@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jglisse@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
/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