From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [gourryinverse:scratch/gourry/managed_nodes/rfc5 34/75] mm/mempolicy.c:1194:3: error: expected ')'
Date: Thu, 25 Jun 2026 05:47:32 +0800 [thread overview]
Message-ID: <202606250535.hKlRhKft-lkp@intel.com> (raw)
tree: https://github.com/gourryinverse/linux scratch/gourry/managed_nodes/rfc5
head: 46a97233124f2cd0a55d11f159f5c975529ebb03
commit: 5a2689d32ea3ed6497b47864893666699f4bb999 [34/75] mm/mempolicy: add in-kernel MPOL_BIND interfaces for drivers/services
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260625/202606250535.hKlRhKft-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260625/202606250535.hKlRhKft-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/202606250535.hKlRhKft-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/mempolicy.c:1194:3: error: expected ')'
1194 | return ERR_PTR(-EINVAL);
| ^
mm/mempolicy.c:1193:5: note: to match this '('
1193 | if (!node_state(nid, N_MEMORY_PRIVATE)
| ^
1 error generated.
vim +1194 mm/mempolicy.c
1172
1173 /**
1174 * mpol_private_bind - build an MPOL_BIND policy pinned to a private node
1175 * @nid: an N_MEMORY_PRIVATE node
1176 *
1177 * Returns a refcounted mempolicy that binds allocations to @nid with the
1178 * private-placement intent (MPOL_F_PRIVATE). This binds to @nid regardless
1179 * of the node's CAP_USER_NUMA, providing a privileged way for node-owners
1180 * to bind driver/service owned VMAs to the node.
1181 *
1182 * Like any MPOL_BIND it is relaxable: an unsatisfiable request falls back
1183 * rather than failing.
1184 *
1185 * Must be called while @nid is N_MEMORY_PRIVATE.
1186 *
1187 * The caller owns the reference and frees it with mpol_put().
1188 *
1189 * Return: the policy, or an ERR_PTR on failure.
1190 */
1191 struct mempolicy *mpol_private_bind(int nid)
1192 {
1193 if (!node_state(nid, N_MEMORY_PRIVATE)
> 1194 return ERR_PTR(-EINVAL);
1195 return __mpol_bind_node(nid, MPOL_F_PRIVATE);
1196 }
1197 EXPORT_SYMBOL_FOR_MODULES(mpol_private_bind, "kmem");
1198
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-24 21:48 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=202606250535.hKlRhKft-lkp@intel.com \
--to=lkp@intel.com \
--cc=gourry@gourry.net \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox