All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev@sw.ru>
To: Jan Kara <jack@suse.cz>
Cc: Kirill Korotaev <dev@openvz.org>,
	devel@openvz.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mark Fasheh <mark.fasheh@oracle.com>
Subject: Re: jbd lost fix?
Date: Mon, 09 Jul 2007 18:26:14 +0400	[thread overview]
Message-ID: <46924586.3000808@sw.ru> (raw)
In-Reply-To: <20070709130021.GA30433@duck.suse.cz>

Jan Kara wrote:
>   Hello,
> 
> On Mon 02-07-07 18:16:09, Kirill Korotaev wrote:
> 
>>it looks like the following fix:
>>http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=43c3e6f5abdf6acac9b90c86bf03f995bf7d3d92
>>
>>was lost after resurrecting of the spliced checkpointing list in this patch:
>>http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=78ce89c92bc6eaf5933b5664bff64253a7103bd7;hp=cdaad343b561cdeb38b0578bb038
>>
>>Can you please confirm that?
> 
>   Sorry for a bit late reply but I was on holiday for a week. Yes, it seems
> like that fix got lost. At least 2.6.22-rc5 still has a wrong test on line
> 890 in commit.c. Thanks for notification, I'll resend it.
>   BTW: How have you found this out?

One of OpenVZ users had an oops at journal_clean_one_cp_list+0x32/0x70
http://bugzilla.openvz.org/show_bug.cgi?id=605

which led us to the lost fix.
Since the patch existed before I didn't dare to resend it from OVZ name :)

Thanks,
Kirill



      reply	other threads:[~2007-07-09 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 14:16 jbd lost fix? Kirill Korotaev
2007-07-09 13:00 ` Jan Kara
2007-07-09 14:26   ` Kirill Korotaev [this message]

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=46924586.3000808@sw.ru \
    --to=dev@sw.ru \
    --cc=dev@openvz.org \
    --cc=devel@openvz.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    /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.