Content-Type: multipart/mixed; boundary="===============9184437259852452268==" MIME-Version: 1.0 From: Chris Down To: kbuild-all@lists.01.org Subject: Re: [PATCH v3 2/2] printk: console: Support console-specific loglevels Date: Thu, 21 Jul 2022 17:29:59 +0100 Message-ID: In-Reply-To: <202207220029.VYxE2uAL-lkp@intel.com> List-Id: --===============9184437259852452268== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable kernel test robot writes: >sparse warnings: (new ones prefixed by >>) >>> kernel/printk/sysctl.c:31:47: sparse: sparse: incorrect type in argumen= t 3 (different address spaces) @@ expected void * @@ got void [node= ref] __user *buffer @@ > kernel/printk/sysctl.c:31:47: sparse: expected void * > kernel/printk/sysctl.c:31:47: sparse: got void [noderef] __user *bu= ffer Ah, since commit 32927393dc1c ("sysctl: pass kernel pointers to = ->proc_handler") we copy to kernelspace before passing to the callback, so = it's = not a userspace pointer. That's certainly an improvement. Will fix for v4. --===============9184437259852452268==--