similar to: [PATCH] 2.4.23 ext3 warning

This patch fixes the data loss which can occur when unmounting a data=journal ext3 filesystem. The core problem is that the VFS doesn't tell the filesystem enough about what is happening. ext3 _needs_ to know the difference between regular memory-cleansing writeback and sync-for-data-integrity purposes. (These two operations are really quite distinct, and the kernel has got it wrong for

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

Hi, We have encountered another funny with ext3 on 2.4. Like the kernel NFS server, we have a routine in InterMezzo that does something like looking up an inode by inode number. (compare intermezzo's presto_ilookup or knfsd's nfsfh_iget) Effectively both of these routines do ilookup() { inode = iget(sb, ino) if (inode->i_nlink==0) iput(inode); .... } We find that

>From nfs-admin@lists.sourceforge.net Thu Feb 1 03:51:36 2001 >Return-Path: <nfs-admin@lists.sourceforge.net> Received: from usw-sf-list1.sourceforge.net (usw-outbound.sourceforge.net [216.136.171.194]) by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id DAA11596 for <jareth@camelot.co.jp>; Thu, 1 Feb 2001 03:51:35 +0900 X-Authentication-Warning:

>From nfs-admin@lists.sourceforge.net Wed Jan 31 09:21:55 2001 >Return-Path: <nfs-admin@lists.sourceforge.net> Received: from usw-sf-list1.sourceforge.net (usw-outbound.sourceforge.net [216.136.171.194]) by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA03106 for <jareth@camelot.co.jp>; Wed, 31 Jan 2001 09:21:53 +0900 X-Authentication-Warning:

Ooops, last one didn't CC ocfs2-devel. On Mon, Oct 13, 2008 at 06:16:15PM -0700, Joel Becker wrote: > @@ -232,25 +231,17 @@ int ocfs2_populate_inode(struct inode *inode, struct ocfs2_dinode *fe, > ocfs2_mount_local(osb) || !ocfs2_stack_supports_plocks()) > use_plocks = 0; > > - /* this means that read_inode cannot create a superblock inode > - * today. change if

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

I'm getting kernel crashes on a new machine since it went into production some weeks ago. How can I troubleshoot this? I suspect a hardware problem, but I know too few about the kernel and kernel debugging on Linux to know how I can nail this down with debugging software. Just for reference of what kind these oopses are I quote the last two. The symptom is that the machine stops

Hi, my program works well with fedora-2 .with fedora-5 it's gives following errors.. get_it_i_say.c:549: warning: implicit declaration of function 'strcmp' cc -o giis dir.o file.o get_it_i_say.o group.o init.o inode.o main.o searchnupdate.o uninit.o inode.o: In function `read_inode':inode.c:(.text+0x202): undefined reference to `S_ISDIR' inode.o: In function

Al writes: > On Thu, 22 Mar 2001, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and

This patch adds freeze_fs()/unfreeze_fs() for ocfs2 so that it supports freeze/thaw. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> --- fs/ocfs2/dlmglue.c | 115 ++++++++++++++++++++++++++++++++++++++++++++++- fs/ocfs2/dlmglue.h | 2 + fs/ocfs2/journal.c | 1 + fs/ocfs2/ocfs2.h | 12 +++++ fs/ocfs2/super.c | 129 +++++++++++++++++++++++++++++++++++++++++++++++++++-

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

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

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 =

Now that the scheduler can deal with migrate disable properly, there is no real compelling reason to make it only available for RT. There are quite some code pathes which needlessly disable preemption in order to prevent migration and some constructs like kmap_atomic() enforce it implicitly. Making it available independent of RT allows to provide a preemptible variant of kmap_atomic() and makes

In the following example, LLVM's logic for merging isomorphic types causes two functions in different compilation units with identical function signatures to have different signatures in the resulting bitcode: =========================== $ cat demo-struct1.c struct foo { int x; }; struct bar { int x; }; struct foo *return_arg_1(struct foo *a, struct bar *b) { return a; } $ cat demo-struct2.c

This patch contains two parts: One is to add a new API to mm go get the unused page information. The virtio balloon driver will use this new API added to get the unused page info and send it to hypervisor(QEMU) to speed up live migration. During sending the bitmap, some the pages may be modified and are used by the guest, this inaccuracy can be corrected by the dirty page logging mechanism. One

Hi All, Is http://thunk.org/tytso/linux/ext3-dxdir/patch-ext3-dxdir-2.4.21rc5 the latest htree patch for 2.4 or should I be using bitkeeper to extract the patch?

Hi! I was updated kernel from 2.4.22 to 2.4.23 and now tc tools can''t correctly determine default (pfifo_fast) qdisc on interface: # tc/tc qdisc ls dev ppp0 qdisc pfifo_fast 0: [Unknown qdisc, optlen=20] but, if I assign f.e. cbq qdisc for some device all show correctly: # tc/tc qdisc ls dev ppp1 qdisc tbf 8009: rate 32Kbit burst 10Kb lat 1.5s qdisc cbq 66: rate 10Mbit