From: Linus Torvalds <torvalds@linux-foundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: kmemleak: Protect the seq start/next/stop sequence by rcu_read_lock()
Date: Wed, 12 Aug 2009 08:32:14 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0908120831060.28882@localhost.localdomain> (raw)
In-Reply-To: <1250079447.20332.27.camel@pc1117.cambridge.arm.com>
On Wed, 12 Aug 2009, Catalin Marinas wrote:
>
> If the object size is bigger than a predefined value (4K in this case),
> release the object lock during scanning and call cond_resched().
What guarantees that the object isn't released during this?
Linus
next prev parent reply other threads:[~2009-08-12 15:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 15:26 [PATCH] " Catalin Marinas
2009-07-30 0:00 ` Andrew Morton
2009-07-30 8:24 ` Catalin Marinas
2009-08-02 11:14 ` Ingo Molnar
2009-08-10 15:55 ` Catalin Marinas
2009-08-10 18:45 ` Ingo Molnar
2009-08-10 22:56 ` Catalin Marinas
2009-08-11 7:32 ` Ingo Molnar
2009-08-11 8:55 ` Catalin Marinas
2009-08-12 12:17 ` Catalin Marinas
2009-08-12 15:32 ` Linus Torvalds [this message]
2009-08-12 15:39 ` Catalin Marinas
2009-08-12 20:52 ` Ingo Molnar
2009-08-12 22:16 ` kmemleak: Protect the seq start/next/stop sequence byrcu_read_lock() Catalin Marinas
2009-08-13 6:52 ` Ingo Molnar
2009-08-13 9:39 ` Catalin Marinas
2009-08-13 9:44 ` Ingo Molnar
2009-08-13 14:44 ` Catalin Marinas
2009-08-14 22:45 ` Catalin Marinas
2009-08-14 22:47 ` [PATCH] kmemleak: Allow rescheduling during an object scanning Catalin Marinas
2009-08-14 22:48 ` [PATCH] kmemleak: Ignore the aperture memory hole on x86_64 Catalin Marinas
2009-08-15 14:17 ` Ingo Molnar
2009-08-15 22:34 ` Catalin Marinas
2009-08-16 7:04 ` Ingo Molnar
2009-08-16 10:08 ` Ingo Molnar
2009-08-16 21:48 ` Catalin Marinas
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=alpine.LFD.2.01.0908120831060.28882@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®