similar to: [PATCH 0/2] ocfs2: two bug fixes about xattr and inline-data

Hi, Thanks Tao and Joel's review, These are the second version of the patches. Mark and Joel, you can correct my comments if you find they don't suitable. thanks, tiger

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 IO or

arrows() seems to hang when either x or y scale of the plot is logarithmic and the arrows requested go beyond the plot (by more than a certain amount). I didn't go into C code to find it, but here's a function that exercises the bug a bit ... arrow.bug2 <- function(y0=1,y1=10,log="y") { plot(c(0.1,1),c(1,10),log=log) arrows(x0=0.5, y0=y0, x1=0.5,

Hey everyone, We're coming up on the next merge window, and I only have a couple tiny fixes for ocfs2. I thought I'd list up what I know is outstanding, and I was hoping to find out if I was missing anything. If I am, I need to get it in linux-next and set for the merge window ASAP. - metaecc-stats This is a trivial patch I put together to track errors seen by the blockcheck code.

I have found a quite strange (to me) behaviour in Sweave. It only occurs in the following situation: 1. define a variable in one chunk 2. use it within a subsequent figure-generating chunk 3. delete it at the end of that same chunk Then the Sweave driver chokes, not finding the variable name when generating the figure Example: % document bug2.Rnw \documentclass{article} \usepackage{Sweave}

>From c70adcaca99acf93bc00cf2edc4d549b83e2f95d Mon Sep 17 00:00:00 2001 From: Wengang Wang <wen.gang.wang at oracle.com> Date: Tue, 21 Jul 2009 10:52:52 +0800 Subject: [PATCH 1/1] ocfs2: adds mlogs to aops.c -V2 this patch adds some mlogs to apos.c helping tracing and narrowing down bugs. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> --- fs/ocfs2/aops.c | 242

This code is undefined, meaning that all bets are off, don't do it. I.e. It reads the value of I between two sequence points and uses it for something other than determining the value written. From: Csaba Raduly Sent: Tuesday, April 19, 2011 3:44 AM To: Joe Armstrong Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Is this a bug in clang? Hi Joe On Tue, Apr 19, 2011 at 10:59 AM, Joe

Hello, Is this a bug in clang, or a bug in my thinking? /Joe Armstrong /* When I compile the following program I get different answers in clang and gcc. $ gcc bug2.c $ ./a.out j = 40 $ clang bug2.c $ ./a.out j = 41 I think the correct answer is 41. If my understanding of C is correct (which, or course, it might not be) the incremented value of i++ is first made available

On Apr 26, 2011, at 2:07 AM, Joe Armstrong wrote: > Compiles (via clang) to: > > ; ModuleID = 'test101.c' > target datalayout = > "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32" > target triple = "i386-pc-linux-gnu" > > define i32 @main() nounwind { > %1 =

So... Are 40 and 41 the only legal behaviors or are there more? Robby On Tuesday, April 19, 2011, Ahmed Charles <ahmedcharles at gmail.com> wrote: > This code is undefined, meaning that all bets are off, don't do it. > I.e. It reads the value of I between two sequence points and uses it > for something other than determining the value written. From: Csaba > Raduly >

I assumed that C floats are 32 bits and doubles 64 bits ... but This code int main(){ float f; double f1; f = 3.145; f1 = 3.145; return(0); } Compiles (via clang) to: ; ModuleID = 'test101.c' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32" target triple =

OK, I am just sending it here too as it looks like r-devel at r-project.org is not the right place: =EF=BB=BFOn Fri, 2008-04-25 at 08:48 +0200, Soeren Sonnenburg wrote: > While trying to fix swig & R2.7 I actually discovered that there is a > bug in R 2.7 causing a crash (so R & swig might actually work): >=20 > the bug is in ./src/main/gram.c line 3038: >=20 >

this patch adds mlogs to apos to help tracing. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> --- fs/ocfs2/aops.c | 233 ++++++++++++++++++++++++++++++++++++++++++++----------- 1 files changed, 189 insertions(+), 44 deletions(-) diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c index b2c52b3..b730010 100644 --- a/fs/ocfs2/aops.c +++ b/fs/ocfs2/aops.c @@ -90,7 +90,7 @@ static int

Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each

Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each

In normal tree rotation left process, we will never touch the tree branch above subtree_index and ocfs2_extend_rotate_transaction doesn't reserve the credits for them either. But when we want to delete the rightmost extent block, we have to update the rightmost records for all the rightmost branch(See ocfs2_update_edge_lengths), so we have to allocate extra credits for them. What's more,

Hi. I introduced "is_partially_uptodate" aops for OCFS2. A page can have multiple buffers and even if a page is not uptodate, some buffers can be uptodate on pagesize != blocksize environment. This aops checks that all buffers which correspond to a part of a file that we want to read are uptodate. If so, we do not have to issue actual read IO to HDD even if a page is not uptodate

Hi, I did some more in-depth testing of OCFS2 quota code, especially with ECC feature enabled and spotted some problems. First four patches fix them. I need the fifth patch to be able to mount OCFS2 filesystem with 2.6.31-rc3. The sixth patch fixes a potential problem when quota syncing interval is updated while the cluster is running (which is not possible currently). Joel, could you please

The patch was created against a 1.4 tree. However, it applies cleanly to mainline too. The patch has been lightly tested. I am running fill_verify_holes on a non sparse volume currently. Please review. Sunil

The patch below does not apply to the 5.10-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable at vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/