linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Ryle <seanbo@gmail.com>
To: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>,
	"Ted Ts'o" <tytso@mit.edu>,
	"615998@bugs.debian.org" <615998@bugs.debian.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org
Subject: Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4
Date: Thu, 23 Jun 2011 16:55:50 -0400	[thread overview]
Message-ID: <BANLkTi=5BLA07tvbv3PFcZ0cc8FmBtg+UA@mail.gmail.com> (raw)
In-Reply-To: <AF621113-8320-4973-A88A-1FC048EA4293@boeing.com>

[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]

Maybe I am wrong here, but shouldn't the cast be to (unsigned long) or to
(sector_t)?

Line 534 of commit.c:
                        jbd_debug(4, "JBD: got buffer %llu (%p)\n",
                                (unsigned long long)bh->b_blocknr,
bh->b_data);

Line 64 of buffer_head.h:
         sector_t b_blocknr;             /* start block number */

Lines 137-143 of include/linux/types/h:
#ifdef CONFIG_LBDAF
typedef u64 sector_t;
typedef u64 blkcnt_t;
#else
typedef unsigned long sector_t;
typedef unsigned long blkcnt_t;
#endif

Is it possible he is experiencing the panic due to a bad cast in the call to
jbd_debug() in fs/jbd2/commit.c?  It would seem to me this should be cast to
(sector_t).  Any thoughts?



On Thu, Jun 23, 2011 at 2:32 PM, Moffett, Kyle D
<Kyle.D.Moffett@boeing.com>wrote:

> Hello again everyone,
>
> I'm in the middle of doing some software testing on a pre-production
> clone of this system using some modified software configurations and a
> testing-only data volume, and I've managed to trigger this panic again.
>
> The trigger was exactly the same; I had a bunch of queued emails from
> logcheck because my TLS configuration was wrong, then I fixed the TLS
> configuration and typed "postqueue -f" to send the queued mail.
>
> Ted, since this new iteration has no customer data, passwords, keys, or
> any other private data, I'm going to try to get approval to release an
> exact EC2 image of this system for you to test with, including the fake
> data volume that I triggered the problem on.
>
> If not I can certainly reproduce it now by stopping email delivery and
> generating a lot of fake syslog spam; I can try applying kernel patches
> and report what happens.
>
> Hopefully you're still willing to help out tracking down the problem?
>
> Thanks again!
>
> Cheers,
> Kyle Moffett
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

[-- Attachment #2: Type: text/html, Size: 2637 bytes --]

  reply	other threads:[~2011-06-23 20:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110301165239.3310.43806.reportbug@support.exmeritus.com>
     [not found] ` <BE4E C1DF-4DFC-4B94-923D-0197B16BD7B4@boeing.com>
2011-03-01 19:26 ` Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG at fs/jbd2/commit.c:534" from Postfix on ext4 Moffett, Kyle D
2011-04-03  2:02   ` Ted Ts'o
2011-04-04 14:24     ` Moffett, Kyle D
2011-04-04 20:51       ` Moffett, Kyle D
2011-04-05  0:15       ` Ted Ts'o
2011-04-05 15:30         ` Moffett, Kyle D
2011-04-05 19:07           ` Ted Ts'o
2011-04-05 19:44             ` Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernelBUG " Moffett, Kyle D
     [not found]               ` <20110405230538.GH2832@thunk.org>
     [not found]                 ` <FD93E462-D97B-411B-BF09-9A64670AC5C2@boeing.com>
2011-06-23 18:32                   ` Bug#615998: linux-image-2.6.32-5-xen-amd64: Repeatable "kernel BUG " Moffett, Kyle D
2011-06-23 20:55                     ` Sean Ryle [this message]
2011-06-23 21:19                       ` Moffett, Kyle D
2011-06-24 13:46                         ` Jan Kara
2011-06-24 16:03                           ` Moffett, Kyle D
2011-06-24 20:02                             ` Jan Kara
2011-06-24 20:51                               ` Kyle Moffett
2011-08-26 21:03                                 ` Moffett, Kyle D
2011-08-30 22:12                                   ` Jan Kara
2011-08-31  0:26                                     ` Moffett, Kyle D
2011-09-01 15:17                                       ` Jan Kara
2011-12-06 21:26                                         ` Moffett, Kyle D
2011-06-27 11:16                               ` Lukas Czerner
2011-06-27 11:57                                 ` Amir Goldstein
2011-06-27 14:02                                 ` Jan Kara
2011-06-27 15:30                                   ` Lukas Czerner
2011-06-27 16:01                                     ` Ted Ts'o
2011-06-27 20:27                                       ` Jan Kara
2011-06-28  4:21                                       ` Moffett, Kyle D
2011-06-28  9:36                                         ` Jan Kara
2011-06-28 13:58                                           ` Ben Hutchings
2011-06-28 14:16                                           ` Ted Ts'o
2011-06-28 19:36                                             ` Moffett, Kyle D
2011-06-28 19:30                                           ` Moffett, Kyle D
2011-06-28 22:57                                             ` Jan Kara
2011-06-29  4:22                                               ` Moffett, Kyle D
2011-06-23 22:23                     ` Ted Ts'o

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='BANLkTi=5BLA07tvbv3PFcZ0cc8FmBtg+UA@mail.gmail.com' \
    --to=seanbo@gmail.com \
    --cc=615998@bugs.debian.org \
    --cc=Kyle.D.Moffett@boeing.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).