2.6.6 breaks kmail (nfs related?)
Hi,
I upgraded from vanilla 2.6.4 to vanilla 2.6.6, using the same compiler (gcc-3.3.1) and .config file (shortened version in attachment) for both. Now I cannot send messages with kmail and I get the following error messages:
...
kmail: Error: Could not add message to folder (No space left on device?)
kmail: WARNING: KMail encountered a fatal error and will terminate now. The error was:KMFolderMaildir::addMsg: abnormally terminating to prevent data loss.
...
Apparently kmail thinks that my /home device is full, but it is not (still ~37GB free). Other programs have no problem writing into my home.
Maybe kmail uses some kind of lock before writing to a folder? (I have fam enabled.) Is it possible that this broke recently?
My home directory is mounted via udp-nfs from a server running vanilla 2.4.25 with a reiserfs on a hardware raid. The mount options on the client are hservnlds:/home /net/hservnlds/home nfs rw,nosuid,nodev,v3,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=sservnlds 0 0
Any hints? This looks like a reproducible regression between 2.6.4 and 2.6.6 to me. I can do more tests on request.
Andreas
Signature · 2 lines
Andreas Amann Institut für Theoretische Physik, TU Berlin
CONFIG_X86=yCONFIG_MMU=yCONFIG_UID16=yCONFIG_GENERIC_ISA_DMA=yCONFIG_EXPERIMENTAL=yCONFIG_CLEAN_COMPILE=yCONFIG_STANDALONE=yCONFIG_SWAP=yCONFIG_SYSVIPC=yCONFIG_SYSCTL=yCONFIG_LOG_BUF_SHIFT=15CONFIG_HOTPLUG=yCONFIG_IKCONFIG=yCONFIG_IKCONFIG_PROC=yCONFIG_KALLSYMS=yCONFIG_FUTEX=yCONFIG_EPOLL=yCONFIG_IOSCHED_NOOP=yCONFIG_IOSCHED_AS=yCONFIG_IOSCHED_DEADLINE=yCONFIG_IOSCHED_CFQ=yCONFIG_MODULES=yCONFIG_MODULE_UNLOAD=yCONFIG_MODULE_FORCE_UNLOAD=yCONFIG_OBSOLETE_MODPARM=yCONFIG_KMOD=yCONFIG_STOP_MACHINE=yCONFIG_X86_PC=yCONFIG_M586=yCONFIG_X86_GENERIC=yCONFIG_X86_CMPXCHG=yCONFIG_X86_XADD=yCONFIG_X86_L1_CACHE_SHIFT=7CONFIG_RWSEM_XCHGADD_ALGORITHM=yCONFIG_X86_PPRO_FENCE=yCONFIG_X86_F00F_BUG=yCONFIG_X86_WP_WORKS_OK=yCONFIG_X86_INVLPG=yCONFIG_X86_BSWAP=yCONFIG_X86_POPAD_OK=yCONFIG_X86_ALIGNMENT_16=yCONFIG_X86_INTEL_USERCOPY=yCONFIG_SMP=yCONFIG_NR_CPUS=32CONFIG_PREEMPT=yCONFIG_X86_LOCAL_APIC=yCONFIG_X86_IO_APIC=yCONFIG_HIGHMEM4G=yCONFIG_HIGHMEM=yCONFIG_MTRR=yCONFIG_IRQBALANCE=yCONFIG_HAVE_DEC_LOCK=yCONFIG_PM=yCONFIG_ACPI_BOOT=yCONFIG_APM=mCONFIG_APM_RTC_IS_GMT=yCONFIG_PCI=yCONFIG_PCI_GOANY=yCONFIG_PCI_BIOS=yCONFIG_PCI_DIRECT=yCONFIG_PCI_MMCONFIG=yCONFIG_PCI_LEGACY_PROC=yCONFIG_PCI_NAMES=yCONFIG_ISA=yCONFIG_PCMCIA_PROBE=yCONFIG_BINFMT_ELF=yCONFIG_BINFMT_AOUT=yCONFIG_PARPORT=mCONFIG_PARPORT_PC=mCONFIG_PARPORT_PC_CML1=mCONFIG_PARPORT_1284=yCONFIG_BLK_DEV_FD=mCONFIG_BLK_DEV_LOOP=mCONFIG_BLK_DEV_CRYPTOLOOP=mCONFIG_BLK_DEV_RAM=mCONFIG_BLK_DEV_RAM_SIZE=4096CONFIG_IDE=yCONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_BLK_DEV_IDECD=mCONFIG_BLK_DEV_IDESCSI=mCONFIG_IDE_GENERIC=yCONFIG_BLK_DEV_IDEPCI=yCONFIG_IDEPCI_SHARE_IRQ=yCONFIG_BLK_DEV_IDEDMA_PCI=yCONFIG_IDEDMA_PCI_AUTO=yCONFIG_BLK_DEV_ADMA=yCONFIG_BLK_DEV_AMD74XX=yCONFIG_BLK_DEV_PIIX=yCONFIG_BLK_DEV_VIA82CXXX=yCONFIG_BLK_DEV_IDEDMA=yCONFIG_IDEDMA_AUTO=yCONFIG_SCSI=mCONFIG_SCSI_PROC_FS=yCONFIG_BLK_DEV_SD=mCONFIG_BLK_DEV_SR=mCONFIG_CHR_DEV_SG=mCONFIG_SCSI_MULTI_LUN=yCONFIG_SCSI_CONSTANTS=yCONFIG_SCSI_AIC7XXX=mCONFIG_AIC7XXX_CMDS_PER_DEVICE=253CONFIG_AIC7XXX_RESET_DELAY_MS=15000CONFIG_AIC7XXX_DEBUG_MASK=0CONFIG_SCSI_QLA2XXX=mCONFIG_NET=yCONFIG_PACKET=yCONFIG_UNIX=yCONFIG_NET_KEY=yCONFIG_INET=yCONFIG_INET_AH=yCONFIG_INET_ESP=yCONFIG_INET_IPCOMP=yCONFIG_IPV6=mCONFIG_NETFILTER=yCONFIG_IP_NF_IPTABLES=mCONFIG_IP_NF_FILTER=mCONFIG_XFRM=yCONFIG_NETDEVICES=yCONFIG_DUMMY=mCONFIG_NET_ETHERNET=yCONFIG_MII=yCONFIG_NET_VENDOR_3COM=yCONFIG_VORTEX=yCONFIG_NET_TULIP=yCONFIG_TULIP=yCONFIG_NET_PCI=yCONFIG_E100=yCONFIG_INPUT=yCONFIG_INPUT_MOUSEDEV=yCONFIG_INPUT_MOUSEDEV_PSAUX=yCONFIG_INPUT_MOUSEDEV_SCREEN_X=1024CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768CONFIG_SOUND_GAMEPORT=yCONFIG_SERIO=yCONFIG_SERIO_I8042=yCONFIG_SERIO_SERPORT=yCONFIG_INPUT_KEYBOARD=yCONFIG_KEYBOARD_ATKBD=yCONFIG_INPUT_MOUSE=yCONFIG_MOUSE_PS2=yCONFIG_VT=yCONFIG_VT_CONSOLE=yCONFIG_HW_CONSOLE=yCONFIG_SERIAL_8250=yCONFIG_SERIAL_8250_CONSOLE=yCONFIG_SERIAL_8250_NR_UARTS=4CONFIG_SERIAL_CORE=yCONFIG_SERIAL_CORE_CONSOLE=yCONFIG_UNIX98_PTYS=yCONFIG_LEGACY_PTYS=yCONFIG_LEGACY_PTY_COUNT=256CONFIG_PRINTER=mCONFIG_AGP=yCONFIG_AGP_INTEL=yCONFIG_AGP_VIA=yCONFIG_I2C=mCONFIG_I2C_CHARDEV=mCONFIG_I2C_ALGOBIT=mCONFIG_I2C_ALGOPCF=mCONFIG_I2C_AMD756=mCONFIG_I2C_ISA=mCONFIG_I2C_PIIX4=mCONFIG_I2C_VIA=mCONFIG_I2C_VIAPRO=mCONFIG_I2C_SENSOR=mCONFIG_SENSORS_VIA686A=mCONFIG_SENSORS_W83781D=mCONFIG_SENSORS_W83L785TS=mCONFIG_VGA_CONSOLE=yCONFIG_DUMMY_CONSOLE=yCONFIG_SOUND=mCONFIG_SND=mCONFIG_SND_TIMER=mCONFIG_SND_PCM=mCONFIG_SND_HWDEP=mCONFIG_SND_RAWMIDI=mCONFIG_SND_OSSEMUL=yCONFIG_SND_MIXER_OSS=mCONFIG_SND_PCM_OSS=mCONFIG_SND_MPU401_UART=mCONFIG_SND_OPL3_LIB=mCONFIG_SND_DUMMY=mCONFIG_SND_MPU401=mCONFIG_SND_AC97_CODEC=mCONFIG_SND_CMIPCI=mCONFIG_SND_ENS1371=mCONFIG_USB=mCONFIG_USB_DEVICEFS=yCONFIG_USB_EHCI_HCD=mCONFIG_USB_OHCI_HCD=mCONFIG_USB_UHCI_HCD=mCONFIG_USB_AUDIO=mCONFIG_USB_PRINTER=mCONFIG_USB_STORAGE=mCONFIG_USB_HID=mCONFIG_USB_HIDINPUT=yCONFIG_USB_HIDDEV=yCONFIG_USB_USBNET=mCONFIG_USB_ALI_M5632=yCONFIG_USB_ARMLINUX=yCONFIG_EXT2_FS=yCONFIG_EXT3_FS=yCONFIG_JBD=yCONFIG_REISERFS_FS=mCONFIG_MINIX_FS=mCONFIG_AUTOFS4_FS=yCONFIG_ISO9660_FS=mCONFIG_JOLIET=yCONFIG_ZISOFS=yCONFIG_ZISOFS_FS=mCONFIG_UDF_FS=mCONFIG_FAT_FS=mCONFIG_MSDOS_FS=mCONFIG_VFAT_FS=mCONFIG_NTFS_FS=mCONFIG_NTFS_RW=yCONFIG_PROC_FS=yCONFIG_PROC_KCORE=yCONFIG_SYSFS=yCONFIG_TMPFS=yCONFIG_RAMFS=yCONFIG_CRAMFS=mCONFIG_NFS_FS=yCONFIG_NFS_V3=yCONFIG_NFSD=yCONFIG_NFSD_V3=yCONFIG_LOCKD=yCONFIG_LOCKD_V4=yCONFIG_EXPORTFS=yCONFIG_SUNRPC=yCONFIG_SMB_FS=mCONFIG_MSDOS_PARTITION=yCONFIG_NLS=yCONFIG_NLS_DEFAULT="iso8859-1"CONFIG_NLS_CODEPAGE_437=mCONFIG_NLS_ISO8859_1=mCONFIG_NLS_ISO8859_15=mCONFIG_EARLY_PRINTK=yCONFIG_X86_FIND_SMP_CONFIG=yCONFIG_X86_MPPARSE=yCONFIG_CRYPTO=yCONFIG_CRYPTO_HMAC=yCONFIG_CRYPTO_NULL=mCONFIG_CRYPTO_MD4=mCONFIG_CRYPTO_MD5=yCONFIG_CRYPTO_SHA1=yCONFIG_CRYPTO_SHA256=mCONFIG_CRYPTO_SHA512=mCONFIG_CRYPTO_DES=yCONFIG_CRYPTO_BLOWFISH=mCONFIG_CRYPTO_TWOFISH=mCONFIG_CRYPTO_SERPENT=mCONFIG_CRYPTO_AES=mCONFIG_CRYPTO_DEFLATE=yCONFIG_CRC32=yCONFIG_ZLIB_INFLATE=yCONFIG_ZLIB_DEFLATE=yCONFIG_X86_SMP=yCONFIG_X86_HT=yCONFIG_X86_BIOS_REBOOT=yCONFIG_X86_TRAMPOLINE=yCONFIG_X86_STD_RESOURCES=yCONFIG_PC=y
Quoted 10 lines · Andreas Amann
I upgraded from vanilla 2.6.4 to vanilla 2.6.6, using the same compiler (gcc-3.3.1) and .config file (shortened version in attachment) for both. Now I cannot send messages with kmail and I get the following error messages:
...
kmail: Error: Could not add message to folder (No space left on device?)
kmail: WARNING: KMail encountered a fatal error and will terminate now. The error was:KMFolderMaildir::addMsg: abnormally terminating to prevent data loss.
Can you strace it to see what the failing system call was? Especially if you can compare the traces between 2.6.4 and 2.6.6 some way..
Trond, any idea?
Linus
På su , 16/05/2004 klokka 00:46, skreiv Linus Torvalds:
Quoted 4 lines
Can you strace it to see what the failing system call was? Especially if you can compare the traces between 2.6.4 and 2.6.6 some way..
Trond, any idea?
Not really: there isn't anything in the NFS filesystem code that can generate an ENOSPC. I agree that the "strace" output will help.
Andreas are both the server and the client running 2.6.6? If so, which do you have to downgrade to 2.6.4 in order to get rid of the error?
Cheers,
Trond
På su , 16/05/2004 klokka 13:59, skreiv Trond Myklebust:
Quoted 2 lines
Andreas are both the server and the client running 2.6.6? If so, which do you have to downgrade to 2.6.4 in order to get rid of the error?
Oh... Another thing that would be useful: mount options please...
Cheers,
Trond
Quoted 2 lines · Trond Myklebust
Oh... Another thing that would be useful: mount options please...
They were in the original email on the kernel mailing list:
hservnlds:/home /net/hservnlds/home nfs rw,nosuid,nodev,v3,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=sservnlds 0
The only thing there is that "intr". Maybe something has broken so that non-lethal signals also trigger errors? That could explain it (partial reads or writes when a timer goes off, or something).
Linus
På su , 16/05/2004 klokka 14:19, skreiv Linus Torvalds:
Quoted 1 line
They were in the original email on the kernel mailing list:
Sorry. I was in Malaysia last week so that email probably drowned in the 1600 other mails I found in my backlog when I returned on Friday. I've found it now in the archives...
Quoted 5 lines
hservnlds:/home /net/hservnlds/home nfs rw,nosuid,nodev,v3,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=sservnlds 0
The only thing there is that "intr". Maybe something has broken so that non-lethal signals also trigger errors? That could explain it (partial reads or writes when a timer goes off, or something).
I haven't touched rpc_clnt_sigmask() in many years, so that would have to be some change to the generic signal handling code.
If kmail really is reporting an ENOSPC, though, then it's hard to see how a signal could produce that particular error.
Cheers,
Trond
Quoted 3 lines · Trond Myklebust
If kmail really is reporting an ENOSPC, though, then it's hard to see how a signal could produce that particular error.
Agreed. But the kmail message is apparently "(No space left on device?)", which may be just kmail itself reacting to a truncated write rather than any actual ENOSPC error. A "strace" would help clarify exactly what goes wrong..
Linus
På su , 16/05/2004 klokka 14:50, skreiv Linus Torvalds:
Quoted 4 lines
Agreed. But the kmail message is apparently "(No space left on device?)", which may be just kmail itself reacting to a truncated write rather than any actual ENOSPC error. A "strace" would help clarify exactly what goes wrong..
Right...
One possible suspect might be open(O_EXCL) since, AFAICS, Andreas is using maildir-style mailboxes. Perhaps that SETATTR call in nfs3_proc_create() is failing? We recently fixed so that it always sets MTIME/ATIME...
Andreas: when you do the "strace" could you first run
echo "16" >/proc/sys/sunrpc/nfs_debug
and then record the output from "dmesg" immediately after the kmail crash?
Cheers,
Trond
Quoted 13 lines · Trond Myklebust
På su , 16/05/2004 klokka 14:50, skreiv Linus Torvalds:
Quoted 4 lines
Agreed. But the kmail message is apparently "(No space left on device?)", which may be just kmail itself reacting to a truncated write rather than any actual ENOSPC error. A "strace" would help clarify exactly what goes wrong..
Right...
One possible suspect might be
open(O_EXCL)since, AFAICS, Andreas is using maildir-style mailboxes. Perhaps that SETATTR call innfs3_proc_create()is failing? We recently fixed so that it always sets MTIME/ATIME...
Quoted 6 lines
Andreas: when you do the "strace" could you first run
echo "16" >/proc/sys/sunrpc/nfs_debug
and then record the output from "dmesg" immediately after the kmail crash?
Ok, I produced the "strace"s and "dmesg"s for the kernels 2.6.4, 2.6.5 and 2.6.6 and made them available at
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/dmesg_kmail_2.6.4
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/dmesg_kmail_2.6.5
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/dmesg_kmail_2.6.6
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/kmail_trace_2.6.4
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/kmail_trace_2.6.5
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/kmail_trace_2.6.6
Some further information:
My problem occurs already with kernel 2.6.5, and it is indeed NFS related (It does not appear on a local home partition).
I reproduced the crash with a server exporting an ext2 partition and one which exports a reiserfs partition. So far I only tested servers running on vanilla 2.4.25. Should I check others?
The mount options according to /proc/mount are
viola:/tmp /net/viola/tmp nfs rw,nosuid,nodev,v3,rsize=8192,wsize=8192,hard,intr,udp,lock,addr=viola 0 0
The traces were produced by the command lines
strace 2>/tmp/kmail_trace_2.6.x /usr/linux-local/kde/bin/kmail --nofork -s test --msg test_mail [email protected]
dmesg > /tmp/dmesg_kmail_2.6.x
(I also tried "strace -f", but apparently exim does not like to be traced?)
Quoted 1 line
From my (limited) point of view, the problem is the ESTALE of an fstat64 call
in the 2.6.5 trace:
Quoted 1 line
access("/net/viola/tmp/amann/home_tmp/Mail/outbox/cur/1084784925.736.utEix:2,S", F_OK) = -1 ENOENT (No such file or directory) rename("/net/viola/tmp/amann/home_tmp/Mail/outbox/tmp/1084784925.736.utEix:2,S", "/net/viola/tmp/amann/home_tmp/Mail/outbox/cur/1084784925 .736.utEix:2,S") = 0
fstat64(8, 0xbfffe650) = -1 ESTALE (Stale NFS file handle) _llseek(8, 0, [373], SEEK_END) = 0 write(8, "X\1\0\0", 4) = -1 ESTALE (Stale NFS file handle)
write(8, "\5\0\0\0,\0\0a\0z\0/\0w\0t\0z\0t\0+\0N\0S\0+\0001\0s"..., 344) = -1 ESTALE (Stale NFS file handle)
<
This succeeds in the 2.6.4 trace:
Quoted 1 line
access("/net/viola/tmp/amann/home_tmp/Mail/outbox/cur/1084785768.460.mTWwO:2,S", F_OK) = -1 ENOENT (No such file or directory) rename("/net/viola/tmp/amann/home_tmp/Mail/outbox/tmp/1084785768.460.mTWwO:2,S", "/net/viola/tmp/amann/home_tmp/Mail/outbox/cur/1084785768 .460.mTWwO:2,S") = 0fstat64(8, {st_mode=S_IFREG|0600, st_size=373, ...}) = 0_llseek(8, 0, [0], SEEK_SET) = 0read(8, "# KMail-Index V1506\n\0\10\0\0\0xV4\22\4\0\0"..., 373) = 373write(8, "X\1\0\0", 4) = 4write(8, "\5\0\0\0,\0\0j\0w\0N\0O\0S\0g\0p\0x\0j\0003\0o\0l\0S"..., 344) = 344 <
In both cases filehandle 8 was generated before by
Quoted 1 line
open("/net/viola/tmp/amann/home_tmp/Mail/.outbox.index", O_RDWR|O_LARGEFILE) = 8
<
No idea what causes the difference.
I hope this is the information you expected. Please let me know what further checks I can do.
Andreas
På må , 17/05/2004 klokka 07:31, skreiv Andreas Amann:
Quoted 5 lines
fstat64(8, 0xbfffe650) = -1 ESTALE (Stale NFS file handle) _llseek(8, 0, [373], SEEK_END) = 0 write(8, "X\1\0\0", 4) = -1 ESTALE (Stale NFS file handle)
write(8, "\5\0\0\0,\0\0a\0z\0/\0w\0t\0z\0t\0+\0N\0S\0+\0001\0s"..., 344)= -1 ESTALE (Stale NFS file handle)
That's wierd... Where could that be coming from? The client is *never* supposed to generate that on its own. If an ESTALE turns up, it should always be generated from the server.
Does that same ESTALE show up on a tcpdump/ethereal dump? If so, could you please check that the filehandle that is contained from the reply to LOOKUP(".outbox.index") is the same as that which is sent on the offending GETATTR call?
Cheers,
Trond
Quoted 8 lines · Trond Myklebust
På må , 17/05/2004 klokka 07:31, skreiv Andreas Amann:
Quoted 6 lines
fstat64(8, 0xbfffe650)= -1 ESTALE (Stale NFS file
handle)_llseek(8, 0, [373], SEEK_END)= 0write(8, "X\1\0\0", 4)= -1 ESTALE (Stale NFS file
handle)write(8, "\5\0\0\0,\0\0a\0z\0/\0w\0t\0z\0t\0+\0N\0S\0+\0001\0s"..., 344)= -1 ESTALE (Stale NFS file handle)
Quoted 8 lines
That's wierd... Where could that be coming from? The client is *never* supposed to generate that on its own. If an ESTALE turns up, it should always be generated from the server.
Does that same ESTALE show up on a tcpdump/ethereal dump? If so, could you please check that the filehandle that is contained from the reply to
LOOKUP(".outbox.index")is the same as that which is sent on the offending GETATTR call?
I now produced the "etheral" dumps and put them on:
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/kmail_etheral_cut_2.6.4
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/kmail_etheral_cut_2.6.6
together with the pertinent "strace"s at:
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/kmail_trace_2.6.4_new
http://wwwnlds.physik.tu-berlin.de/~amann/kmail_bug/kmail_trace_2.6.6_new
I interpret the dump in the failing case with the 2.6.6 client as follows:
First the Filehandle for ".outbox.index" (0xdc36f60a) is delivered by a READDIRPLUS Reply (Frame 4 in kmail_etheral_cut_2.6.6). Then the client does GETATTR, ACCESS, SETATTR, READ (Frames 100-114) without any problems. The client subsequnetly issues a WRITE and a COMMIT (Frame 741 + 751) command, which are still successful. But the immediadetly following GETATTR (Frame
743) fails with ERR_STALE.
In the case where the client is 2.6.4, the dumps look very similar, except that now a lot of the GETATTR Calls are missing. In particular the GETATTR which failed in the 2.6.6 case is not present, and therefore can not fail.
In both cases the server was 2.4.25. Who is now wrong in this case, the client or the server? To me it looks now, as if the server needs to be fixed, but I am no expert.
Andreas
På fr , 21/05/2004 klokka 11:27, skreiv Andreas Amann:
Quoted 3 lines
In both cases the server was 2.4.25. Who is now wrong in this case, the client or the server? To me it looks now, as if the server needs to be fixed, but I am no expert.
Yep. This is a server side bug. I just checked the dump, and the client is indeed sending the correct filehandle (exactly the same one as in the COMMIT just before it).
Hmm... It looks to me as if you are exporting that filesystem with the "subtree_check" option enabled. Could you try to set "no_subtree_check"? The subtree checking stuff breaks NFS in various subtle ways (including renames etc), and is one of the more common sources of ESTALE errors.
Cheers,
Trond
Quoted 3 lines · Trond Myklebust
Hmm... It looks to me as if you are exporting that filesystem with the "
subtree_check" option enabled. Could you try to set "no_subtree_check"?
Thanks for that one, with "no_subtree_check" the problem disappears! What is the disadvantage of this option?
Andreas
Quoted 7 lines · Andreas Amann
Quoted 3 lines · Trond Myklebust
Hmm... It looks to me as if you are exporting that filesystem with the "
subtree_check" option enabled. Could you try to set "no_subtree_check"?Thanks for that one, with "
no_subtree_check" the problem disappears! What is the disadvantage of this option?
With "no_subtree_check" the server will not attempt to verify that a given filehandle points to a file that is beneath an exported directory; thus an attacker can guess filehandles of files not beneath any exported directory and use those guessed filehandles to acces files you didn't mean to export.
Even with "no_subtree_check", the server can still recognize which filesystem a filehandle belongs to; so you're only in trouble if you have files you don't want exported on the same partition as files you do want exported.
See "man exports" for more.
--Bruce Fields
Quoted 1 line · Andreas Amann
(I also tried "strace -f", but apparently exim does not like to be traced?)
Exim's setuid. Tracing setuid programs generally is fraught with peril, especially if that program changes uids, drops privileges and then re-execs itself (as exim does, IIRC). :-/
Signature · 1 line
Matthias Urlichs
Quoted 5 lines · Andreas Amann
kmail: Error: Could not add message to folder (No space left on device?)
kmail: WARNING: KMail encountered a fatal error and will terminate now. The error was:KMFolderMaildir::addMsg: abnormally terminating to prevent data loss.
...
Well, I'm getting this with kcalc after upgrading to 2.6.6-mm3:
$ kcalc KCrash: Application 'kcalc' crashing...
strace shows lots of
...
close(1002) = -1 EBADF (Bad file descriptor) close(1003) = -1 EBADF (Bad file descriptor) close(1004) = -1 EBADF (Bad file descriptor) close(1005) = -1 EBADF (Bad file descriptor)
...
Now it's late. More tests and info tomorrow (unless there's a new -mm kernel which fixes this :-) )
Regards,
Norberto
Quoted 6 lines · Norberto Bensa
Well, I'm getting this with kcalc after upgrading to 2.6.6-mm3:
$ kcalc KCrash: Application 'kcalc' crashing...
Quoted 7 lines
strace shows lots of
...close(1002) = -1 EBADF (Bad file descriptor) close(1003) = -1 EBADF (Bad file descriptor) close(1004) = -1 EBADF (Bad file descriptor) close(1005) = -1 EBADF (Bad file descriptor)...
Send the whole thing, please: strace -f -o log kcalc', and send log'. If it's too big to post please mail it to me direct and I'll stick it on a public server.
Thanks.
Quoted 16 lines · Andrew Morton
Quoted 6 lines · Norberto Bensa
Well, I'm getting this with kcalc after upgrading to 2.6.6-mm3:
$ kcalc KCrash: Application 'kcalc' crashing...Quoted 7 lines
strace shows lots of
...close(1002) = -1 EBADF (Bad file descriptor) close(1003) = -1 EBADF (Bad file descriptor) close(1004) = -1 EBADF (Bad file descriptor) close(1005) = -1 EBADF (Bad file descriptor)...
Quoted 4 lines
Send the whole thing, please:
strace -f -o log kcalc', and sendlog'. If it's too big to post please mail it to me direct and I'll stick it on a public server.
Norberto's strace log is at
http://www.zip.com.au/~akpm/linux/patches/stuff/log.txt
På må , 17/05/2004 klokka 13:35, skreiv Andrew Morton:
Quoted 2 lines
Norberto's strace log is at
http://www.zip.com.au/~akpm/linux/patches/stuff/log.txt
A priori, it looks very different from Andreas' problem. This beast is crashing due to a SIGSEGV.
The EBADF here appear to be correct: the application or glibc or whatever appears to be trying to close files more than once. Duh...
Cheers,
Trond
Quoted 6 lines · Norberto Bensa
Well, I'm getting this with kcalc after upgrading to 2.6.6-mm3:
$ kcalc KCrash: Application 'kcalc' crashing...
Quoted 6 lines
strace shows lots of
...close(1002) = -1 EBADF (Bad file descriptor) close(1003) = -1 EBADF (Bad file descriptor) close(1004) = -1 EBADF (Bad file descriptor) close(1005) = -1 EBADF (Bad file descriptor)
Looks like daemonizing code to me, getting rid of open fds.
Signature · 1 line
Frank