From: EUNBONG SONG <eunb.song@samsung.com>
To: Tony Luck <tony.luck@gmail.com>, Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re: Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+
Date: Mon, 13 May 2013 02:21:05 +0000 (GMT) [thread overview]
Message-ID: <7032562.14371368411664268.JavaMail.weblogic@epml07> (raw)
> CONFIG_IA64_PAGE_SIZE_64KB=y
> fsblock size is whatever is the default for SLES11SP2 on ia64 - which
> tool will tell me?
> My git bisect finally competed and points the a finger at:
> bisect> git bisect good
> ae4647fb7654676fc44a97e86eb35f9f06b99f66 is first bad commit
> commit ae4647fb7654676fc44a97e86eb35f9f06b99f66
> Author: Jan Kara
> Date: Fri Apr 12 00:03:42 2013 -0400
> jbd2: reduce journal_head size
> Remove unused t_cow_tid field (ext4 copy-on-write support doesn't seem
> to be happening) and change b_modified and b_jlist to bitfields thus
> saving 8 bytes in the structure.
> Signed-off-by: Jan Kara
> Signed-off-by: "Theodore Ts'o"
> Reviewed-by: Zheng Liu
> :040000 040000 c39ece4341894b3daf84764ba425a87ffb90fe50
> d4e8d9185c2a1b740c235ca8ed05d496a442fce3 M include
Hi, my git bisect result is same yours. And i reported that to community yesterday.
Thanks.
next reply other threads:[~2013-05-13 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 2:21 EUNBONG SONG [this message]
2013-05-13 3:11 ` Re: Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+ Tony Luck
2013-05-13 3:36 ` Theodore Ts'o
2013-05-13 5:18 ` Mike Galbraith
2013-05-13 6:14 ` Tony Luck
-- strict thread matches above, loose matches on Subject: below --
2013-05-13 9:53 Re: " EUNBONG SONG
2013-05-13 11:26 ` Zheng Liu
2013-05-13 12:07 ` Dmitry Monakhov
2013-05-13 12:54 ` Eunbong Song
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=7032562.14371368411664268.JavaMail.weblogic@epml07 \
--to=eunb.song@samsung.com \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@gmail.com \
--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).