Re: [linux-next:master 4172/4394] drivers/block/loop.c:413 lo_rw_aio() error: we previously assumed 'file' could be null (see line 400)

[Dan Carpenter <error27@gmail.com>]

On Sat, May 09, 2026 at 10:32:06PM +0900, Tetsuo Handa wrote:
> On 2026/05/09 22:19, Dan Carpenter wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   e98d21c170b01ddef366f023bbfcf6b31509fa83
> > commit: 1a83d226268cfb9ea546febe6515f39584df8fd2 [4172/4394] loop: check refcount in __loop_clr_fd() and lo_rw_aio()
> > config: m68k-randconfig-r073-20260509 (https://download.01.org/0day-ci/archive/20260509/202605092030.FAH71Jou-lkp@intel.com/config)
> > compiler: m68k-linux-gcc (GCC) 12.5.0
> > smatch: v0.5.0-9065-ge9cc34fd
> > 
> > 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>
> > | Reported-by: Dan Carpenter <error27@gmail.com>
> > | Closes: https://lore.kernel.org/r/202605092030.FAH71Jou-lkp@intel.com/
> > 
> > New smatch warnings:
> > drivers/block/loop.c:413 lo_rw_aio() error: we previously assumed 'file' could be null (see line 400)
> 
> Thanks, but this is intentional in order to get reported
> at https://syzkaller.appspot.com/bug?extid=cd8a9a308e879a4e2c28
> after printing debug information.

With these zero day bots, I just have access to the email which you see,
not the commit itself.  Maybe one idea is we add a comment when we're
adding linux-next only debug code?

On the other hand, reviewing and sending these emails is very fast and
costs me no time at all so I don't mind either way.

regards,
dan carpenter