linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@tv-sign.ru>
To: Torsten Kaiser <just.for.lkml@googlemail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Alasdair G Kergon <agk@redhat.com>,
	Milan Broz <mbroz@redhat.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debug_check_no_locks_freed: fix in_range() checks
Date: Sat, 24 Nov 2007 15:25:11 +0300	[thread overview]
Message-ID: <20071124122511.GA2219@tv-sign.ru> (raw)
In-Reply-To: <64bb37e0711240418i2e90916dx3f1b622df0e2f8b3@mail.gmail.com>

On 11/24, Torsten Kaiser wrote:
>
> On Nov 24, 2007 11:53 AM, Oleg Nesterov <oleg@tv-sign.ru> wrote:
> > Torsten, could you ack/nack this patch?
> 
> From looking at the code I would ack it.

Great.

> I will reapply agk-dm-dm-crypt-move-bio-submission-to-thread.patch and
> this patch and boot several times, but as the message was not
> triggered on every boot, this can't prove anything.

Regardless of any other possible problems, I think you found a real bug
in debug_check_no_locks_freed() which should be fixed.

Oleg.


  reply	other threads:[~2007-11-24 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071120234605.GG23667@elte.hu>
2007-11-21 15:58 ` 2.6.24-rc2-mm1: kcryptd vs lockdep Oleg Nesterov
2007-11-21 16:06   ` Johannes Berg
2007-11-24 10:53   ` [PATCH] debug_check_no_locks_freed: fix in_range() checks Oleg Nesterov
2007-11-24 12:18     ` Torsten Kaiser
2007-11-24 12:25       ` Oleg Nesterov [this message]
2007-11-24 12:35       ` Alasdair G Kergon
2007-11-24 12:22     ` Ingo Molnar

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=20071124122511.GA2219@tv-sign.ru \
    --to=oleg@tv-sign.ru \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=just.for.lkml@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=mingo@elte.hu \
    /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).