VFS programming / PANIC when opening new files
Jelmer Vernooij
jelmer at nl.linux.org
Mon Apr 28 01:27:23 GMT 2003
Try samba and the skel module from current 3_0 CVS. Please report if
you still get segfaults.
Jelmer
On Sun, Apr 27, 2003 at 08:50:45PM +0200, Joachim wrote about 'VFS programming / PANIC when opening new files':
> After I had some problems (=hang ups/PANICs) with a (my) small VFS module, I
> found out that as soon as I Drag&Drop a new (!!) file on a share with this
> module enabled, successful calls to "open", "ftruncate" and "lock" are
> made. But then, the corresponding smbd panics (log follows):
> [2003/04/27 19:59:43, 4] smbd/open.c:open_file_shared1(969)
> calling open_file with flags=0x1 flags2=0xC0 mode=0746
> [2003/04/27 19:59:43, 2] smbd/open.c:open_file(240)
> nobody opened file home/tester2/CALLISTO.CAB read=No write=Yes (numopen=1)
> [2003/04/27 19:59:43, 8] lib/util.c:is_in_path(1483)
> is_in_path: home/tester2/CALLISTO.CAB
> [2003/04/27 19:59:43, 8] lib/util.c:is_in_path(1487)
> is_in_path: no name list.
> [2003/04/27 19:59:43, 5] smbd/oplock.c:set_file_oplock(218)
> set_file_oplock: granted oplock on file home/tester2/CALLISTO.CAB, dev =
> 1608, inode = 193690, file_id = 1, tv_sec = 3eac1a8f, tv_usec = ef02f
> [2003/04/27 19:59:43, 0] lib/fault.c:fault_report(36)
> ===============================================================
> [2003/04/27 19:59:43, 0] lib/fault.c:fault_report(37)
> INTERNAL ERROR: Signal 11 in pid 744 (3.0alpha23)
> Please read the file BUGS.txt in the distribution
> [2003/04/27 19:59:43, 0] lib/fault.c:fault_report(39)
> ===============================================================
> [2003/04/27 19:59:43, 0] lib/util.c:smb_panic(1412)
> smb_panic: clobber_region() last called from [set_share_mode(633)]
> [2003/04/27 19:59:43, 0] lib/util.c:smb_panic(1429)
> PANIC: internal error
> Opening existing files for writing is no problem!
> Now I took skel.c again, compiled it wihout (!!) any modifications, moved to
> my Windows machine, browsed the tree of the share, opened files ... etc. At
> the same time I looked at the PID of the smbd for the connection - result:
> as soon as a new file is created, the smbd for the connection dies and a
> new one is started (with a PANIC in log file)!!??
> At the beginning I thought MY own code/module is faulty. But now it is same
> effect with skel.c!
> BTW: Samba 3.0alpha23, Linux 2.4.20, gcc 3.2, glibc 2.3.? (Slackware 8.1,
> updated a little bit)
> Joachim
--
Jelmer Vernooij <jelmer at nl.linux.org> - http://nl.linux.org/~jelmer/
03:26:21 up 8:22, 10 users, load average: 0.18, 0.10, 0.08
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20030428/629cae8f/attachment.bin
More information about the samba-technical
mailing list