Hi,
it seems that ext4/btrfs code for fallocate doesn't check for
immutable/append inode flag. I think it's possible to do an fallocate
operation even if the immutable flag is turned on. You can think about
this case: an application opens a file for read/write, meanwhile a user
set the immutable
HPET doesn't use timer_interrupt() as interrupt handler now. So count of
HPET interrupt isn't recorded in per_cpu(irq_stat, cpu).irq0_irqs. This
confuses NMI watchdog when using HPET as tick device.
Signed-off-by: Yan, Zheng zheng.z@intel.com
---
diff --git a/arch/x86/include/asm/hardirq.h
Sent this mail to wrong list, sorry for interrupting.
Yan, Zheng
On Wed, Dec 29, 2010 at 9:57 AM, Yan, Zheng zheng.z@linux.intel.com wrote:
HPET doesn't use timer_interrupt() as interrupt handler now. So count of
HPET interrupt isn't recorded in per_cpu(irq_stat, cpu).irq0_irqs. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I was installing Kbuntu 10.10 in a VirtualBox 3.2.12 VM when I ran into
a BUG. My system kept running, but my Kbuntu install failed, and the
VirtualBox instance was impossible to kill. (Killing the VirtualBox
program with xkill removed the
On 2010-12-28, at 09:06, Marco Stornelli wrote:
it seems that ext4/btrfs code for fallocate doesn't check for
immutable/append inode flag.
fallocate() probably shouldn't be allowed for immutable files, but it makes a
lot of sense to call fallocate() on append-only files to avoid fragmentation,
