From: kernel test robot <lkp@intel.com>
To: Tarun Sahu <tarunsahu@google.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: mm/memfd_luo.c:404:32: error: incompatible type for argument 1 of 'phys_to_virt'
Date: Wed, 01 Jul 2026 12:55:08 +0200 [thread overview]
Message-ID: <202607011209.2J1vgY7B-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Tarun-Sahu/kho-add-KHOSER_COPY_PTR-to-allow-phys-copy-of-serialized-ptr/20260623-195248
head: 324baa84cbf51b0e981cfb3b684037a4e4862433
commit: 324baa84cbf51b0e981cfb3b684037a4e4862433 luo: Update serialized data to use KHOSER_PTR
date: 8 days ago
config: x86_64-rhel-9.4-kselftests (https://download.01.org/0day-ci/archive/20260701/202607011209.2J1vgY7B-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260701/202607011209.2J1vgY7B-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607011209.2J1vgY7B-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/memfd_luo.c: In function 'memfd_luo_finish':
>> mm/memfd_luo.c:404:32: error: incompatible type for argument 1 of 'phys_to_virt'
404 | ser = phys_to_virt(args->serialized_data);
| ~~~~^~~~~~~~~~~~~~~~~
| |
| union <anonymous>
In file included from include/linux/io.h:12,
from mm/memfd_luo.c:76:
arch/x86/include/asm/io.h:148:46: note: expected 'phys_addr_t' {aka 'long long unsigned int'} but argument is of type 'union <anonymous>'
148 | static inline void *phys_to_virt(phys_addr_t address)
| ~~~~~~~~~~~~^~~~~~~
mm/memfd_luo.c: In function 'memfd_luo_retrieve':
mm/memfd_luo.c:531:32: error: incompatible type for argument 1 of 'phys_to_virt'
531 | ser = phys_to_virt(args->serialized_data);
| ~~~~^~~~~~~~~~~~~~~~~
| |
| union <anonymous>
arch/x86/include/asm/io.h:148:46: note: expected 'phys_addr_t' {aka 'long long unsigned int'} but argument is of type 'union <anonymous>'
148 | static inline void *phys_to_virt(phys_addr_t address)
| ~~~~~~~~~~~~^~~~~~~
vim +/phys_to_virt +404 mm/memfd_luo.c
b3749f174d6866 Pratyush Yadav 2025-11-25 386
b3749f174d6866 Pratyush Yadav 2025-11-25 387 static void memfd_luo_finish(struct liveupdate_file_op_args *args)
b3749f174d6866 Pratyush Yadav 2025-11-25 388 {
b3749f174d6866 Pratyush Yadav 2025-11-25 389 struct memfd_luo_folio_ser *folios_ser;
b3749f174d6866 Pratyush Yadav 2025-11-25 390 struct memfd_luo_ser *ser;
b3749f174d6866 Pratyush Yadav 2025-11-25 391
f85b1c6af5bc38 Pratyush Yadav (Google 2026-02-16 392) /*
f85b1c6af5bc38 Pratyush Yadav (Google 2026-02-16 393) * If retrieve was successful, nothing to do. If it failed, retrieve()
f85b1c6af5bc38 Pratyush Yadav (Google 2026-02-16 394) * already cleaned up everything it could. So nothing to do there
f85b1c6af5bc38 Pratyush Yadav (Google 2026-02-16 395) * either. Only need to clean up when retrieve was not called.
f85b1c6af5bc38 Pratyush Yadav (Google 2026-02-16 396) */
f85b1c6af5bc38 Pratyush Yadav (Google 2026-02-16 397) if (args->retrieve_status)
b3749f174d6866 Pratyush Yadav 2025-11-25 398 return;
b3749f174d6866 Pratyush Yadav 2025-11-25 399
324baa84cbf51b Tarun Sahu 2026-06-23 400 ser = KHOSER_LOAD_PTR(args->serialized_data);
324baa84cbf51b Tarun Sahu 2026-06-23 401 if (!ser)
b3749f174d6866 Pratyush Yadav 2025-11-25 402 return;
b3749f174d6866 Pratyush Yadav 2025-11-25 403
5968408926aa37 Tarun Sahu 2026-06-23 @404 ser = phys_to_virt(args->serialized_data);
5968408926aa37 Tarun Sahu 2026-06-23 405
b3749f174d6866 Pratyush Yadav 2025-11-25 406 if (ser->nr_folios) {
b3749f174d6866 Pratyush Yadav 2025-11-25 407 folios_ser = kho_restore_vmalloc(&ser->folios);
b3749f174d6866 Pratyush Yadav 2025-11-25 408 if (!folios_ser)
b3749f174d6866 Pratyush Yadav 2025-11-25 409 goto out;
b3749f174d6866 Pratyush Yadav 2025-11-25 410
b3749f174d6866 Pratyush Yadav 2025-11-25 411 memfd_luo_discard_folios(folios_ser, ser->nr_folios);
b3749f174d6866 Pratyush Yadav 2025-11-25 412 vfree(folios_ser);
b3749f174d6866 Pratyush Yadav 2025-11-25 413 }
b3749f174d6866 Pratyush Yadav 2025-11-25 414
b3749f174d6866 Pratyush Yadav 2025-11-25 415 out:
b3749f174d6866 Pratyush Yadav 2025-11-25 416 kho_restore_free(ser);
b3749f174d6866 Pratyush Yadav 2025-11-25 417 }
b3749f174d6866 Pratyush Yadav 2025-11-25 418
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-01 10:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607011209.2J1vgY7B-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tarunsahu@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.