search for: s_lock

...his implicitly triggers the writebehind on sync(). */ -static int do_sync_supers = 0; -MODULE_PARM(do_sync_supers, "i"); -MODULE_PARM_DESC(do_sync_supers, "Write superblocks synchronously"); - void ext3_write_super (struct super_block * sb) { + if (down_trylock(&sb->s_lock) == 0) + BUG(); + sb->s_dirt = 0; + log_start_commit(EXT3_SB(sb)->s_journal, NULL); +} + +static int ext3_sync_fs(struct super_block *sb) +{ tid_t target; - if (down_trylock(&sb->s_lock) == 0) - BUG(); /* aviro detector */ sb->s_dirt = 0; target = log_start_commit(EXT3_S...

...ernel 2.4.8), and I ran the patch. I believe there were something like 4 hunks that fialed. I was able to go do these manually. While doing these, I noticed the filesystem stuff between 2.4.8 and 2.4.4 has changed drastically. I also had to comment out the the lines: if (down_trylock(&sb->s_lock) == 0) BUG(); in ext3_write_super(), because s_lock is not a semaphore in 2.4.4, its just a char being 1 for locked, 0 for unlocked. Once I did this, it compiled and booted up OK. I then converted the root file system (/dev/hda1) to ext3 by running tune2fs -j /dev/hda1. I then edited /etc/fstab...

...#39; isn't known include/linux/fs.h:447: error: storage size of `i_data' isn't known include/linux/fs.h:574: error: storage size of `f_owner' isn't known include/linux/fs.h:745: error: storage size of `s_umount' isn't known include/linux/fs.h:746: error: storage size of `s_lock' isn't known include/linux/fs.h:773: error: storage size of `s_vfs_rename_sem' isn't known {standard input}: Assembler messages: {standard input}:747: Error: symbol `rv' is already defined {standard input}:761: Error: symbol `rv' is already defined {standard input}:768: Erro...

I already did what you said,please see the log results in zaptel.rar attached when I compile zapltel using make ********************************************* No employee or agent is authorized to conclude any binding agreement on behalf of Xplorium with another party by e-mail without express written confirmation by an officer of Xplorium. Any views expressed by an individual in this

On Thu, Sep 3, 2015 at 6:45 PM, Kostya Serebryany <kcc at google.com> wrote: > Did you build the Postgres code with -fsanitize-coverage=... ? Yes: CC = clang CFLAGS = -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -Wno-unused-command-line-argument -g -O0 -fsanitize=address

...3_sb_info *sbi = EXT3_SB(sb); struct ext3_super_block *es = sbi->s_es; @@ -2018,7 +2003,7 @@ * This implicitly triggers the writebehind on sync(). */ -void ext3_write_super (struct super_block * sb) +static void ext3_write_super (struct super_block * sb) { if (down_trylock(&sb->s_lock) == 0) BUG(); @@ -2041,7 +2026,7 @@ * LVM calls this function before a (read-only) snapshot is created. This * gives us a chance to flush the journal completely and mark the fs clean. */ -void ext3_write_super_lockfs(struct super_block *sb) +static void ext3_write_super_lockfs(struct supe...

I am using centos 4.4 server cd ,when I am trying to compile zaptel 1.4.2 ... error appears > >From where I can get the missing rpms .or kernel source >From where I can get the centos 4.4 server kernel source. Regards ********************************************* No employee or agent is authorized to conclude any binding agreement on behalf of Xplorium with another

...storage/ipc/shm_mq.o storage/ipc/shm_toc.o > storage/ipc/sinval.o storage/ipc/sinvaladt.o storage/ipc/standby.o > storage/large_object/inv_api.o storage/lmgr/lmgr.o storage/lmgr/lock.o > storage/lmgr/proc.o storage/lmgr/deadlock.o storage/lmgr/lwlock.o > storage/lmgr/spin.o storage/lmgr/s_lock.o storage/lmgr/predicate.o > storage/page/bufpage.o storage/page/checksum.o storage/page/itemptr.o > storage/smgr/md.o storage/smgr/smgr.o storage/smgr/smgrtype.o > tcop/dest.o tcop/fastpath.o tcop/postgres.o tcop/pquery.o > tcop/utility.o tsearch/ts_locale.o tsearch/ts_parse.o > tse...