From: Jiri Slaby <jirislaby@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>, kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [tty:tty-next 27/37] drivers/tty/vt/keyboard.c:1712:7: error: cannot jump from this asm goto statement to one of its possible targets
Date: Tue, 25 Nov 2025 06:51:57 +0100 [thread overview]
Message-ID: <2fe33f3d-562a-4382-9aef-e50eb5a97772@kernel.org> (raw)
In-Reply-To: <20251124221343.GA2953435@ax162>
On 24. 11. 25, 23:13, Nathan Chancellor wrote:
> On Mon, Nov 24, 2025 at 06:25:26PM +0800, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-next
>> head: da218406dd50e0ac96bb383de4edd208286efe70
>> commit: bfb24564b5fd8625ce5c007f274cabdc3b570969 [27/37] tty: vt/keyboard: use __free()
>> config: powerpc-randconfig-002-20251124 (https://download.01.org/0day-ci/archive/20251124/202511241835.EA8lShgH-lkp@intel.com/config)
>> compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251124/202511241835.EA8lShgH-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/202511241835.EA8lShgH-lkp@intel.com/
>>
>> All errors (new ones prefixed by >>):
>>
>>>> drivers/tty/vt/keyboard.c:1712:7: error: cannot jump from this asm goto statement to one of its possible targets
>> if (put_user(asize, &a->kb_cnt))
>> ^
>> arch/powerpc/include/asm/uaccess.h:67:5: note: expanded from macro 'put_user'
>> __put_user(x, _pu_addr) : -EFAULT; \
>> ^
>> arch/powerpc/include/asm/uaccess.h:49:3: note: expanded from macro '__put_user'
>> __put_user_size_goto(__pu_val, __pu_addr, __pu_size, __pu_failed); \
>> ^
>> arch/powerpc/include/asm/uaccess.h:127:10: note: expanded from macro '__put_user_size_goto'
>> case 1: __put_user_asm_goto(x, __pus_addr, label, "stb"); break; \
>> ^
>> arch/powerpc/include/asm/uaccess.h:87:2: note: expanded from macro '__put_user_asm_goto'
>> asm goto( \
>> ^
>> drivers/tty/vt/keyboard.c:1736:7: note: possible target of asm goto statement
>> if (put_user(asize, &a->kb_cnt))
>> ^
>> arch/powerpc/include/asm/uaccess.h:67:5: note: expanded from macro 'put_user'
>> __put_user(x, _pu_addr) : -EFAULT; \
>> ^
>> arch/powerpc/include/asm/uaccess.h:53:9: note: expanded from macro '__put_user'
>> \
>> ^
>> drivers/tty/vt/keyboard.c:1692:33: note: jump exits scope of variable with __attribute__((cleanup))
>> struct kbdiacr __free(kfree) *dia = kmalloc_array(MAX_DIACR, sizeof(struct kbdiacr),
>> ^
>> drivers/tty/vt/keyboard.c:1722:23: note: jump bypasses initialization of variable with __attribute__((cleanup))
>> void __free(kfree) *buf = kmalloc_array(MAX_DIACR, sizeof(struct kbdiacruc),
>> ^
>
> Previously reported:
>
> https://lore.kernel.org/202509091702.Oc7eCRDw-lkp@intel.com/
Ah, I forgot about this :(.
> My suggested workaround in that thread is still applicable if it would
> be acceptable as a formal patch:
>
> https://lore.kernel.org/20250909215342.GA2456480@ax162/
I think it makes sense. Could you post it formally then?
thanks,
--
js
suse labs
prev parent reply other threads:[~2025-11-25 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 10:25 [tty:tty-next 27/37] drivers/tty/vt/keyboard.c:1712:7: error: cannot jump from this asm goto statement to one of its possible targets kernel test robot
2025-11-24 22:13 ` Nathan Chancellor
2025-11-25 5:51 ` Jiri Slaby [this message]
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=2fe33f3d-562a-4382-9aef-e50eb5a97772@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--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