All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: Valerie Clement <valerie.clement@bull.net>,
	Alex Tomas <alex@clusterfs.com>,
	Andreas Dilger <adilger@clusterfs.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: performance testing
Date: Tue, 26 Jun 2007 11:48:46 +0200	[thread overview]
Message-ID: <4680E0FE.8080102@bull.net> (raw)
In-Reply-To: <4680CE9B.1030602@bull.net>

Valerie Clement wrote:
> Alex Tomas wrote:
>> Jean noel Cordenner wrote:
>>> The last patch queue concerns the  2.6.22-rc4 kernel, so we took the
>>> previous ext4 patch queue including the modifications suggested by 
>>> dmitriy:
>>> http://article.gmane.org/gmane.comp.file-systems.ext4/2291
>>> This solve the oops problem but after a while, the system hangs. We are
>>> still trying to find where the bug is.
>>> When we remove all the patches until booked-page-flag.patch in the
>>> series, the system still hangs. When using another filesystem, or
>>> whithout any patches it works.
>>
>> any details? backtraces? dmesg?
> 
> We are trying to get some traces, but with 2.6.22-rc5 and 2.6.22-rc6 
> kernels, the serial console isn't working on our systems (x86_64), the 
> magic SysRq keys either. Strange...
> 
> When the system hangs, no messages are logged.
> It seems that the hangs only occur with ext4 FS when applying the 
> patches of the current git tree.
> We are trying now to find which patch is faulty.
> 
>    Valérie
> 

It seems that the faulty patch is "ext4-journal_chksum-2.6.20.patch".
Looking at the patch, I think the following change is not correct:

@@ -116,21 +120,36 @@ static int journal_write_commit_record(j

     bh = jh2bh(descriptor);

-   /* AKPM: buglet - add `i' to tmp! */
     for (i = 0; i < bh->b_size; i += 512) {
-       journal_header_t *tmp = (journal_header_t*)bh->b_data;
+       struct commit_header *tmp = (struct commit_header*)bh->b_data +
+                                           i;

Shouldn't it be :

   struct commit_header *tmp = (struct commit_header*)(bh->b_data + i);

Valérie

       reply	other threads:[~2007-06-26  9:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <467BE4C0.2020203@bull.net>
     [not found] ` <1182541578.9939.3.camel@localhost.localdomain>
     [not found]   ` <467C99F5.6060603@clusterfs.com>
     [not found]     ` <1182755567.4067.1.camel@localhost.localdomain>
     [not found]       ` <467FE8A5.4030508@bull.net>
     [not found]         ` <467FEAF7.7060902@clusterfs.com>
     [not found]           ` <4680CE9B.1030602@bull.net>
2007-06-26  9:48             ` Valerie Clement [this message]
2007-06-26 10:36               ` performance testing Girish Shilamkar
2007-06-26 11:03                 ` Valerie Clement
2014-09-17  8:48 Performance testing Jan Tulak
2014-09-17  9:36 ` Dmitry Monakhov
2014-09-25 15:08   ` Jan Tulak
2014-09-18  0:36 ` Dave Chinner
2014-09-25 15:03   ` Jan Tulak
2014-09-27  0:47     ` Dave Chinner
2014-09-29 16:07       ` Jan Tulak
2014-10-25 17:10       ` Jan Tulak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4680E0FE.8080102@bull.net \
    --to=valerie.clement@bull.net \
    --cc=adilger@clusterfs.com \
    --cc=alex@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.