public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-fsdevel@vger.kernel.org
Subject: Re: [viro-vfs:work.fd 11/19] fs/select.c:860:3: error: cannot jump from this goto statement to its label
Date: Fri, 7 Jun 2024 16:24:28 +0100	[thread overview]
Message-ID: <20240607152428.GY1629371@ZenIV> (raw)
In-Reply-To: <202406071836.yx9rpD7U-lkp@intel.com>

On Fri, Jun 07, 2024 at 06:47:54PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.fd
> head:   e0288728ff8a4703675c4c8e2ea8a0122b7675f6
> commit: 3cc074209e634318e4f9fd4a813dae7703d2aa78 [11/19] switch simple users of fdget() to CLASS(fd, ...)
> config: s390-allnoconfig (https://download.01.org/0day-ci/archive/20240607/202406071836.yx9rpD7U-lkp@intel.com/config)
> compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project d7d2d4f53fc79b4b58e8d8d08151b577c3699d4a)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240607/202406071836.yx9rpD7U-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/202406071836.yx9rpD7U-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
[loads of noise, then]

> >> fs/select.c:860:3: error: cannot jump from this goto statement to its label
>      860 |                 goto out;
>          |                 ^
>    fs/select.c:862:12: note: jump bypasses initialization of variable with __attribute__((cleanup))
>      862 |         CLASS(fd, f)(fd);
>          |                   ^
>    13 warnings and 1 error generated.

Sigh...  That's why declarations in the middle of block really stink.
Sadly, the use of CLASS() very much invites that kind of crap.
For this series I decided to suppress the gag reflex and see how
it goes, but... ouch.

Worse, neither current gcc, nor clang 14 catch that kind of crap ;-/

  reply	other threads:[~2024-06-07 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 10:47 [viro-vfs:work.fd 11/19] fs/select.c:860:3: error: cannot jump from this goto statement to its label kernel test robot
2024-06-07 15:24 ` Al Viro [this message]
2024-06-07 20:20   ` Nathan Chancellor
2024-06-07 20:30     ` Al Viro

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=20240607152428.GY1629371@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lkp@intel.com \
    --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