All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-desktop 36/36] drivers/block/zram/zram_ioctl.c:128:23: error: alignment may not be specified for 'pidfd'
Date: Thu, 26 Mar 2026 09:13:32 +0800	[thread overview]
Message-ID: <202603260907.3cpvyJ4i-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android16-6.12-desktop
head:   f7b5f6381c3c4402de70d091e7db40ef4606c7c4
commit: 160a4092db67397d85b790f102f375ae0e045257 [36/36] ANDROID: zram: Add ZRAM_ANDROID_IOC_PROCESS_PREFETCH ioctl
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20260326/202603260907.3cpvyJ4i-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260326/202603260907.3cpvyJ4i-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/202603260907.3cpvyJ4i-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/block/zram/zram_ioctl.c:128:23: error: alignment may not be specified for 'pidfd'
     128 |         __aligned_u64 pidfd,

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for INTEL_MEI_ME
   Depends on [n]: X86 && PCI [=y]
   Selected by [y]:
   - INTEL_MEI_HDCP [=y] && (DRM_I915 [=n] || DRM_XE [=y])
   - INTEL_MEI_PXP [=y] && (DRM_I915 [=n] || DRM_XE [=y])


vim +/pidfd +128 drivers/block/zram/zram_ioctl.c

   126	
   127	static int zram_ioctl_process_scan(struct zram *zram, unsigned int cmd,
 > 128		__aligned_u64 pidfd,
   129		struct zram_android_ioc_process_range_writeback *prwb,
   130		struct zram_pp_ctl *ctl)
   131	{
   132		struct mm_struct *mm;
   133		struct vm_area_struct *vma;
   134		struct task_struct *task;
   135		unsigned long start_addr = 0;
   136		u64 nr_remaining_pages = 0;
   137		unsigned int f_flags;
   138		int ret = 0;
   139	
   140		struct zram_process_walk_private private = {
   141			.zram = zram,
   142			.pp_ctl = ctl,
   143			.cmd = cmd,
   144		};
   145	
   146		if (cmd == ZRAM_ANDROID_IOC_PROCESS_RANGE_WRITEBACK) {
   147			start_addr = (unsigned long)prwb->start_addr;
   148			nr_remaining_pages = DIV_ROUND_UP_POW2(prwb->size, PAGE_SIZE);
   149		}
   150	
   151		if (!nr_remaining_pages)
   152			private.nr_remaining_pages = NR_PAGES_UNLIMITED;
   153		else
   154			private.nr_remaining_pages = nr_remaining_pages;
   155	
   156		task = pidfd_get_task(pidfd, &f_flags);
   157		if (IS_ERR(task))
   158			return PTR_ERR(task);
   159	
   160		mm = get_task_mm(task);
   161		if (!mm) {
   162			ret = -ESRCH;
   163			goto release_task;
   164		}
   165	
   166		if (start_addr >= mm->task_size) {
   167			ret = -EINVAL;
   168			goto release_mm;
   169		}
   170	
   171		if (!IS_ALIGNED(start_addr, PAGE_SIZE)) {
   172			ret = -EINVAL;
   173			goto release_mm;
   174		}
   175	
   176		VMA_ITERATOR(vmi, mm, start_addr);
   177		/* Iterates through all the VMAs of the process */
   178		mmap_read_lock(mm);
   179		for_each_vma(vmi, vma) {
   180			unsigned long start = max(vma->vm_start, start_addr);
   181	
   182			if (!vma_is_anonymous(vma) && (!can_do_file_pageout(vma) &&
   183						       (vma->vm_flags & VM_MAYSHARE)))
   184				continue;
   185	
   186			ret = walk_page_range(mm, start, vma->vm_end,
   187					      &zram_walk_ops, &private);
   188			if (ret)
   189				break;
   190		}
   191	
   192		if (cmd == ZRAM_ANDROID_IOC_PROCESS_RANGE_WRITEBACK) {
   193			if (ret > 0) {
   194				prwb->next_addr = private.next_addr;
   195				ret = 0;
   196			} else {
   197				prwb->next_addr = 0;
   198			}
   199		}
   200	
   201		mmap_read_unlock(mm);
   202	release_mm:
   203		mmput(mm);
   204	release_task:
   205		put_task_struct(task);
   206	
   207		return ret;
   208	}
   209	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-03-26  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  1:13 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-07  4:01 [android-common:android16-6.12-desktop 36/36] drivers/block/zram/zram_ioctl.c:128:23: error: alignment may not be specified for 'pidfd' kernel test robot

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=202603260907.3cpvyJ4i-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.