search for: i_alloc_sem

Former logic of ocfs2_file_aio_write() was a bit stricky to unlock the rw_lock and i_alloc_sem, by using some private bits in struct 'iocb' to communite with ocfs2_dio_end_io(), it did work before we introduce the patch of supporting 'coherency=full,buffered' option, since rw_lock and i_alloc_sem were never acquired both at the same time, no mattar we doing buffered or direct...

i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it''s use case in the core direct I/O code is more like a counter given that the writers already have external seriali...

...e' isn't known include/linux/fs.h:432: error: storage size of `i_mtime' isn't known include/linux/fs.h:433: error: storage size of `i_ctime' isn't known include/linux/fs.h:440: error: storage size of `i_sem' isn't known include/linux/fs.h:441: error: storage size of `i_alloc_sem' 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...

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

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