similar to: [patch] fix the ext3 data=journal unmount bug

There are three patches at http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.20/ sync_fs.patch: Fix the ext3 data=journal data-loss-on-unmount bug sync_fs-fix.patch: Fix sync_fs.patch to not deadlock the fs when running `mount -o remount' against a heavily loaded filesystem. ext3-use-after-free.patch Fix a use-after-free bug which can cause memory corruption if the filesystem runs

Hello Andrew, I patched 2.4.20 with your patch found out on http://lwn.net/Articles/17447/ and I have a big problem with: once server is booted on 2.4.20 with your patch, when I want to reboot with /sbin/reboot, server makes a Segmentation fault and it crashs. I tested it on 50-60 servers and it is the same problem. I tested kernel 2.4.20 without your patch: no problem. # uname -a Linux XXXXXX

Hi Andrew, The patch below addresses the problem we were talking about earlier where ext3_writepage ends up accessing the inode after the page lock has been dropped (and hence at a point where it is possible for the inode to have been reclaimed.) Tested minimally (it builds and boots.) It makes ext3_journal_stop take an sb, not an inode, as its final parameter. It also sets

The patch below contains the following cleanups: - make some needlessly global code static - super.c: remove the unused global function ext3_panic Please comment ib whether this patch is correct or conflicts with pending changes. diffstat output: fs/ext3/balloc.c | 2 fs/ext3/dir.c | 2 fs/ext3/inode.c | 4 fs/ext3/resize.c | 4

Remove the initialisation of read_inode() super op from BTRFS as it has been dropped. Signed-off-by: David Howells <dhowells@redhat.com> --- fs/btrfs/super.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index a46300c..612a34f 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@ -462,7 +462,6 @@ static struct

this doesn't do anything but noisy debug printks anymore Index: src/super.c =================================================================== --- src/super.c (revision 1426) +++ src/super.c (working copy) @@ -196,9 +196,7 @@ static struct super_operations ocfs_sops = { .statfs = ocfs_statfs, - .put_inode = ocfs_put_inode, .clear_inode = ocfs_clear_inode, - //put_inode =

Hello. I found bugs on error handlings in the functions arround the ext3 file system, which cause inadequate completions of synchronous write I/O operations when disk I/O failures occur. Both 2.4 and 2.6 have this problem. I carried out following experiment: 1. Mount a ext3 file system on a SCSI disk with ordered mode. 2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT

Hello, I have a question about device number extension in "e2fsprogs-1.35". In Linux kernel 2.6, device number is extended from 16-bit to 32-bit. All utilities and libraries should make corresponding extension for this new feature in kernel 2.6. Following operation defines type "kdev_t" as "unsigned short" type, thus the device number has only 16-bit. In file

Greetings all, I have a question regarding the fsync data corruption bug that was introduced in 2.4.20 when using data=journal. I have patched the 2.4.20 kernel with the 3 sync patches available from zip.com.au, and I am wondering if with these patches the "bug" still exists: sync_fs.patch sync_fs-fix.patch sync_fs-fix-2.patch In addition the following two patches have also

The difference between kdev_t and dev_t in 2.4 is rather theoretical, no need to clutter up the source for it. Index: src/inode.c =================================================================== --- src/inode.c (revision 969) +++ src/inode.c (working copy) @@ -1877,11 +1872,8 @@ case OCFS_ATTRIB_FIFO: case OCFS_ATTRIB_SOCKET: { -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)

Using kernel 2.4.20 with the following patches ext3-scheduling-storm.patch ext3-use-after-free.patch sync_fs-fix-2.patch sync_fs-fix.patch sync_fs.patch Note: this problem started happening before applying the patches I have a small partition for / since I don't have much there. Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda6 303344 98934

Andi Kleen <ak at suse.de> writes: > As far as I can see there is nothing in ocfs2_ioctl that requires the BKL, > so use unlocked_ioctl Mark, can you please ack/nack this patch and ideally take it into your tree? You're the only file system maintainer who hasn't acknowledged yet. Thanks, -Andi

It's both in 2.6 and recent 2.6 (for RH ASS2.1 you'll probably need to copy the latest 2.4 defintion, but I don't care for obsolete junk). Index: src/super.c =================================================================== --- src/super.c (revision 1014) +++ src/super.c (working copy) @@ -799,7 +799,7 @@ /* get first two blocks */ for (i=0; i<2; i++) { - bhs[i] = getblk

Asterisk - 1.8.4.1 Dahdi-linux - 2.4.1.2 Dahdi-tools - 2.4.1 Kernel: 2.6.37.6 Kernel BKL: enabled I am upgrading Asterisk on this box. It has an OpenVox A400P PCI analog card with 1 FXO and 1FXS module. This server has been running just fine for two years with Asterisk 1.6.1.0 I've just upgraded all the OS and installed Asterisk 1.8.4.1. On trying to configure the A400P I get: # modprobe

Patches against 2.4.10-pre4 and 2.4.9-ac9 are at http://www.uow.edu.au/~andrewm/linux/ext3/ It's a fairly large change. The most significant parts are * the inclusion of Stephen's error-handling work, which is designed to remount the fs read-only in the presence of software and hardware errors, rather than forcing a panic. * Stephen's fix for the journal_revoke assertion

# HG changeset patch # User inakoshi.hiroya@jp.fujitsu.com # Date 1191287395 -28800 # Node ID 5543e74774a826b1781893982ed5052312b820fc # Parent 83239b2890723e0c06bad507bb273a970784b18e Flush stdout when xentop -b gets SIGINT and SIGTERM. It is useful when you stop xentop -b by keyboard interrupt or by other programs such as killall from a batch script. You would have missed the bottom part of

Kill warning if CONFIG_QUOTA is disabled. --- linux-2.4.23/fs/ext3/super.c.orig Fri Nov 28 21:04:40 2003 +++ linux-2.4.23/fs/ext3/super.c Sun Nov 30 12:16:00 2003 @@ -449,7 +449,6 @@ } static struct dquot_operations ext3_qops; -static int (*old_sync_dquot)(struct dquot *dquot); static struct super_operations ext3_sops = { read_inode: ext3_read_inode, /* BKL held */ @@ -1773,6 +1772,8 @@

Hi, on my c6.3 server (guest of a vmware host) I have a strange load average value: w command: > [root at s-doc ~]# w > 11:19:23 up 41 days, 23:15, 1 user, load average: 4,03, 4,03, 4,00 > USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT > root pts/2 dodo:S.0 11:15 0.00s 0.02s 0.00s w top command: > top - 12:13:31 up 42 days, 9 min, 1

Hi Chris- Here''s a simpler version of the patch that drops the unrelated sync_fs stuff. thanks- sage The ''flushoncommit'' mount option forces any data dirtied by a write in a prior transaction to commit as part of the current commit. This makes the committed state a fully consistent view of the file system from the application''s perspective (i.e., it

An ext3 update for Alan's latest kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The version of ext3 in -ac kernels currently stands at 0.9.6, so this is a fairly large diff. However most of this code has had a decent amount of external testing via the 0.9.9 patch. The changelog since 0.9.6 is below. Please test it if you can, and all being well we shall ask Alan to merge it a