Displaying 3 results from an estimated 3 matches for "ext3_journal_current_handle".
2005 Nov 24
2
Assertion failure in ext3_sync_file() at fs/ext3/fsync.c:50: "ext3_journal_current_handle() == 0"
------------[ cut here ]------------
kernel BUG at fs/ext3/fsync.c:50!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<b0187d38>] Not tainted VLI
EFLAGS: 00010296 (2.6.13.1)
EIP is at ext3_sync_file+0x58/0xf0
eax: 00000068 ebx: bf4a479c ecx: b03cffac edx: b03cffac
esi: b0398cfc edi: b2b8f1c8 ebp: c13bcf60 esp: c13bcf18
ds: 007b es: 007b ss: 0068
Process aptitude
2005 Jan 09
0
[PATCH] ext3: s/0/NULL/ in pointer context
...l.ru>
Index: linux-2.6.10-bk11-warnings/fs/ext3/inode.c
===================================================================
--- linux-2.6.10-bk11-warnings/fs/ext3/inode.c (revision 11)
+++ linux-2.6.10-bk11-warnings/fs/ext3/inode.c (revision 12)
@@ -803,7 +803,7 @@
if (create) {
handle = ext3_journal_current_handle();
- J_ASSERT(handle != 0);
+ J_ASSERT(handle != NULL);
}
ret = ext3_get_block_handle(handle, inode, iblock,
bh_result, create, 1);
@@ -876,7 +876,7 @@
bh = sb_getblk(inode->i_sb, dummy.b_blocknr);
if (buffer_new(&dummy)) {
J_ASSERT(create != 0);
- J_ASSERT(handle != 0...
2004 Sep 16
1
[PATCH] BUG on fsync/fdatasync with Ext3 data=journal
Hello,
We found that fsync and fdatasync syscalls sometimes don't sync
data in an ext3 file system under the following conditions.
1. Kernel version is 2.6.6 or later (including 2.6.8.1 and 2.6.9-rc2).
2. Ext3's journalling mode is "data=journal".
3. Create a file (whose size is 1Mbytes) and execute umount/mount.
4. lseek to a random position within the file, write 8192 bytes