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:android14-kiwi-6.1 353/353] mm/oom_kill.c:753: warning: Function parameter or member 'tsk' not described in '__mark_oom_victim'
Date: Tue, 27 Oct 2026 16:15:53 +0100	[thread overview]
Message-ID: <202610271653.nagh3VDs-lkp@intel.com> (raw)

Hi zhengtangquan,

FYI, the error/warning still remains.

tree:   https://android.googlesource.com/kernel/common android14-kiwi-6.1
head:   b0800a06decb0c4d9b0e0a7f3ad4d38cb76e946a
commit: 6e5f1821281fd8b67e7033f3a07d14d4d18588f9 [353/353] ANDROID: signal: Add vendor hook for memory reap
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20261027/202610271653.nagh3VDs-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/20261027/202610271653.nagh3VDs-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/202610271653.nagh3VDs-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> mm/oom_kill.c:753: warning: Function parameter or member 'tsk' not described in '__mark_oom_victim'
>> mm/oom_kill.c:753: warning: expecting prototype for tsk(). Prototype was for __mark_oom_victim() instead


vim +753 mm/oom_kill.c

   747	
   748	/**
   749	 * tsk->mm has to be non NULL and caller has to guarantee it is stable (either
   750	 * under task_lock or operate on the current).
   751	 */
   752	static void __mark_oom_victim(struct task_struct *tsk)
 > 753	{
   754		struct mm_struct *mm = tsk->mm;
   755	
   756		if (!cmpxchg(&tsk->signal->oom_mm, NULL, mm)) {
   757			mmgrab(tsk->signal->oom_mm);
   758		}
   759	}
   760	

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

                 reply	other threads:[~2026-10-27 15:16 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=202610271653.nagh3VDs-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.