]> www.infradead.org Git - nvme.git/commit
mm/migrate: make migrate_misplaced_folio() return 0 on success
authorDavid Hildenbrand <david@redhat.com>
Thu, 20 Jun 2024 21:29:34 +0000 (23:29 +0200)
committerAndrew Morton <akpm@linux-foundation.org>
Thu, 4 Jul 2024 02:30:26 +0000 (19:30 -0700)
commit4b88c23ab8c9bc3857f7c8847e2c6bed95185530
tree16c3dfb2cb9ba1a16491d4b8d1a0b430dbe29113
parent7d6be67cfdd4a53cea7147313ca13c531e3a470f
mm/migrate: make migrate_misplaced_folio() return 0 on success

Patch series "mm/migrate: move NUMA hinting fault folio isolation + checks
under PTL".

Let's just return 0 on success, which is less confusing.

...  especially because we got it wrong in the migrate.h stub where we
have "return -EAGAIN; /* can't migrate now */" instead of "return 0;".
Likely this wrong return value doesn't currently matter, but it certainly
adds confusion.

We'll add migrate_misplaced_folio_prepare() next, where we want to use the
same "return 0 on success" approach, so let's just clean this up.

Link: https://lkml.kernel.org/r/20240620212935.656243-1-david@redhat.com
Link: https://lkml.kernel.org/r/20240620212935.656243-2-david@redhat.com
Signed-off-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Zi Yan <ziy@nvidia.com>
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Donet Tom <donettom@linux.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
mm/huge_memory.c
mm/memory.c
mm/migrate.c