Re: kern/55699: Panic certainly in iSCSI initiator

[BERTRAND Joël <joel.bertrand%systella.fr@localhost>]

The following reply was made to PR kern/55699; it has been noted by GNATS.

From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= <joel.bertrand%systella.fr@localhost>
To: Paul Goyette <paul%whooppee.com@localhost>
Cc: kern-bug-people%netbsd.org@localhost,
        "gnats-bugs%netbsd.org@localhost"
 <gnats-bugs%NetBSD.org@localhost>,
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/55699: Panic certainly in iSCSI initiator
Date: Wed, 7 Oct 2020 18:20:31 +0200

 Paul Goyette a écrit :
 > On Wed, 7 Oct 2020, BERTRAND Joël wrote:
 > 
 >> Paul Goyette a écrit :
 >>> That confirms that the module is being auto-loaded and -unloaded
 >>>
 >>> So now we just have to identify where it is being used-after-unload.
 >>
 >> Â Â Â Â Yes, I understand, but I don't see how this trouble can be related to
 >> bacula. I have checked in sources and I haven't find any line of code
 >> related to ab usb device.
 > 
 > Something in bacula is invoking usbdevs, either directly or via the
 > same ioctl.  Perhaps it is in some library dependency?  I don't know,
 > I don't use bacula.  But that's what triggers your crash.
 
 In bacula's sources (src/findlib/fstype.c), I see that is called (line 127).
 
 statvfs is a libc function :
 
 int
 statvfs(const char *file, struct statvfs *st)
 {
     return statvfs1(file, st, ST_WAIT);
 }
 
 but I don't find sources of statvfs1 (seems to be statvfs1.S) to check
 if this function call usbdevs.
 
 	JKB