Re: One minute delay when booting 2.6.24.1
On Saturday 09 February 2008 22:01:44 Jan Engelhardt wrote: > On Feb 9 2008 13:29, Tvrtko A. Ursulin wrote: > >Hi all, > > > >As the subject says I get ~1 minute delay when booting 2.6.24.1 > >pretty reliably. It is possible it is not new to 2.6.24.1 but I > >can't tell due recent hardware changes. > > > >dmesg excerpt where it happens looks like this (full one attached): > > Do you really experience a 1 minute wait, or is this perhaps > just the clock skipping? This seemed to slipped everyone's attention so I took the liberty of copying a couple of you guys. I don't know better than to guess it could something to do with timers or scheduling so apologies if you are not the right people. As said in my previous reply it is a real ~60 second delay early in the boot process with some logs attached in my initial report. Thanks, Tvrtko -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: One minute delay when booting 2.6.24.1
On Saturday 09 February 2008 22:01:44 Jan Engelhardt wrote: On Feb 9 2008 13:29, Tvrtko A. Ursulin wrote: Hi all, As the subject says I get ~1 minute delay when booting 2.6.24.1 pretty reliably. It is possible it is not new to 2.6.24.1 but I can't tell due recent hardware changes. dmesg excerpt where it happens looks like this (full one attached): Do you really experience a 1 minute wait, or is this perhaps just the clock skipping? This seemed to slipped everyone's attention so I took the liberty of copying a couple of you guys. I don't know better than to guess it could something to do with timers or scheduling so apologies if you are not the right people. As said in my previous reply it is a real ~60 second delay early in the boot process with some logs attached in my initial report. Thanks, Tvrtko -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: One minute delay when booting 2.6.24.1
On Saturday 09 February 2008 22:01:44 Jan Engelhardt wrote: > On Feb 9 2008 13:29, Tvrtko A. Ursulin wrote: > >Hi all, > > > >As the subject says I get ~1 minute delay when booting 2.6.24.1 > >pretty reliably. It is possible it is not new to 2.6.24.1 but I > >can't tell due recent hardware changes. > > > >dmesg excerpt where it happens looks like this (full one attached): > > Do you really experience a 1 minute wait, or is this perhaps > just the clock skipping? It is a real delay. Tvrtko -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: One minute delay when booting 2.6.24.1
On Saturday 09 February 2008 22:01:44 Jan Engelhardt wrote: On Feb 9 2008 13:29, Tvrtko A. Ursulin wrote: Hi all, As the subject says I get ~1 minute delay when booting 2.6.24.1 pretty reliably. It is possible it is not new to 2.6.24.1 but I can't tell due recent hardware changes. dmesg excerpt where it happens looks like this (full one attached): Do you really experience a 1 minute wait, or is this perhaps just the clock skipping? It is a real delay. Tvrtko -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Out of tree module using LSM
Hi Linus, all, During one recent LKML discussion (http://marc.info/?l=linux-kernel=119267398722085=2) about LSM going static you called for LSM users to speak up. We here at Sophos (the fourth largest endpoint security vendor in the world) have such a module called Talpa which is a part of our main endpoint security product for Linux that protects from viruses and malware hosted on Linux, including those targetting Windows or other connected devices, (http://www.sophos.com/products/enterprise/endpoint/security-and-control/linux/index.html) which is GPL code and has been in the field for almost three years now. It's source code has been shipping with the product from the start. We also have a SourceForge project at http://sourceforge.net/projects/talpa/ to host it. In essence, what our module does is it intercepts file accesses and allows userspace daemons to vet them. One of the means we implemented that is through LSM and although it is not a perfect match for such use we prefer to use an official interface. Unfortunately, with time it became impossible to use LSM on some distributions (SELinux) so we had to implement other intercept methods which are significantly less nice, and which may also become unworkable over time. The main point here is that making LSM not available for modules makes our life even more difficult and we would like to ask you to revert that change until another acceptable, secure solution is found. At this point I would not like this to turn into a discussion on technical or code merits of our current approach. It is just that usage scenarios of (dis-)allowing access to files based on their content, regardless of the actual details, do sound like a reasonable idea. What we would like to do is to start discussion about possible solutions in which other interested parties will hopefully join and in future create some progress on this front. -- Tvrtko August Ursulin Senior Software Engineer, Sophos Tel: 01235 559933 Web: www.sophos.com Protecting business against viruses, spyware, spam and policy abuse Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Out of tree module using LSM
Hi Linus, all, During one recent LKML discussion (http://marc.info/?l=linux-kernelm=119267398722085w=2) about LSM going static you called for LSM users to speak up. We here at Sophos (the fourth largest endpoint security vendor in the world) have such a module called Talpa which is a part of our main endpoint security product for Linux that protects from viruses and malware hosted on Linux, including those targetting Windows or other connected devices, (http://www.sophos.com/products/enterprise/endpoint/security-and-control/linux/index.html) which is GPL code and has been in the field for almost three years now. It's source code has been shipping with the product from the start. We also have a SourceForge project at http://sourceforge.net/projects/talpa/ to host it. In essence, what our module does is it intercepts file accesses and allows userspace daemons to vet them. One of the means we implemented that is through LSM and although it is not a perfect match for such use we prefer to use an official interface. Unfortunately, with time it became impossible to use LSM on some distributions (SELinux) so we had to implement other intercept methods which are significantly less nice, and which may also become unworkable over time. The main point here is that making LSM not available for modules makes our life even more difficult and we would like to ask you to revert that change until another acceptable, secure solution is found. At this point I would not like this to turn into a discussion on technical or code merits of our current approach. It is just that usage scenarios of (dis-)allowing access to files based on their content, regardless of the actual details, do sound like a reasonable idea. What we would like to do is to start discussion about possible solutions in which other interested parties will hopefully join and in future create some progress on this front. -- Tvrtko August Ursulin Senior Software Engineer, Sophos Tel: 01235 559933 Web: www.sophos.com Protecting business against viruses, spyware, spam and policy abuse Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.24-rc] pdflush stuck in D state
Hi all, So as the subject says - pdflush is stuck i D state which means constant load average of at least one: root 151 0.0 0.0 0 0 ?DNov20 0:33 [pdflush] I get this behaviour on both my home and my work machine, which are significantly different hardware but probably almost identical core kernel config. Also, rc version is deliberately not specified because I've seen the problem at home with -rc1 and at work with -rc3. Later is also patched with CFS v24 but the former wasn't so that's probably irrelevant. Some information attached below and I am happy to provide more, although due to lack of time can't promise I'll be able to bisect. FilesystemTypeSize Used Avail Use% Mounted on /dev/sda5 jfs 12G 5.2G 6.0G 47% / varrun tmpfs 1014M 412K 1014M 1% /var/run varlock tmpfs 1014M 0 1014M 0% /var/lock udev tmpfs 1014M 92K 1014M 1% /dev devshm tmpfs 1014M 0 1014M 0% /dev/shm /dev/sda1 ext3122M 60M 56M 52% /boot /dev/sda7 jfs 38G 9.2G 29G 25% /home /dev/sda8 jfs 95G 14G 81G 15% /storage /dev/sda6 jfs3.8G 390M 3.4G 11% /var none tmpfs6.0G 480K 6.0G 1% /tmp allegro:/share nfs 20G 11G 9.7G 52% /mnt/allegro magnum:/share nfs 21G 17G 3.8G 82% /mnt/magnu, crescendo:/talpa nfs205G 189G 17G 92% /talpa //uk-filer1.green.sophos/users smbfs680G 421G 260G 62% /home/tvrtko/mnt/filer /dev/scd0 iso9660464M 464M 0 100% /media/cdrom0 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.24-rc3-cfs-v24 # Tue Nov 20 09:59:58 2007 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_X86_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=17 # CONFIG_CGROUPS is not set CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y # CONFIG_FAIR_CGROUP_SCHED is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set #
[2.6.24-rc] pdflush stuck in D state
Hi all, So as the subject says - pdflush is stuck i D state which means constant load average of at least one: root 151 0.0 0.0 0 0 ?DNov20 0:33 [pdflush] I get this behaviour on both my home and my work machine, which are significantly different hardware but probably almost identical core kernel config. Also, rc version is deliberately not specified because I've seen the problem at home with -rc1 and at work with -rc3. Later is also patched with CFS v24 but the former wasn't so that's probably irrelevant. Some information attached below and I am happy to provide more, although due to lack of time can't promise I'll be able to bisect. FilesystemTypeSize Used Avail Use% Mounted on /dev/sda5 jfs 12G 5.2G 6.0G 47% / varrun tmpfs 1014M 412K 1014M 1% /var/run varlock tmpfs 1014M 0 1014M 0% /var/lock udev tmpfs 1014M 92K 1014M 1% /dev devshm tmpfs 1014M 0 1014M 0% /dev/shm /dev/sda1 ext3122M 60M 56M 52% /boot /dev/sda7 jfs 38G 9.2G 29G 25% /home /dev/sda8 jfs 95G 14G 81G 15% /storage /dev/sda6 jfs3.8G 390M 3.4G 11% /var none tmpfs6.0G 480K 6.0G 1% /tmp allegro:/share nfs 20G 11G 9.7G 52% /mnt/allegro magnum:/share nfs 21G 17G 3.8G 82% /mnt/magnu, crescendo:/talpa nfs205G 189G 17G 92% /talpa //uk-filer1.green.sophos/users smbfs680G 421G 260G 62% /home/tvrtko/mnt/filer /dev/scd0 iso9660464M 464M 0 100% /media/cdrom0 # # Automatically generated make config: don't edit # Linux kernel version: 2.6.24-rc3-cfs-v24 # Tue Nov 20 09:59:58 2007 # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_QUICKLIST=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y # CONFIG_GENERIC_TIME_VSYSCALL is not set # CONFIG_ZONE_DMA32 is not set CONFIG_ARCH_POPULATES_NODE_MAP=y # CONFIG_AUDIT_ARCH is not set CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_X86_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y CONFIG_KTIME_SCALAR=y CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION= # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_USER_NS is not set # CONFIG_PID_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_LOG_BUF_SHIFT=17 # CONFIG_CGROUPS is not set CONFIG_FAIR_GROUP_SCHED=y CONFIG_FAIR_USER_SCHED=y # CONFIG_FAIR_CGROUP_SCHED is not set CONFIG_SYSFS_DEPRECATED=y CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_ANON_INODES=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_SLUB_DEBUG=y # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_SLOB is not set CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # CONFIG_BLK_DEV_BSG is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=cfq # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is
