From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, linville@tuxdriver.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: clear cfg80211_inform_bss() from kmemleak reports
Date: Thu, 03 Sep 2009 20:17:17 +0200 [thread overview]
Message-ID: <1252001837.9336.2.camel@johannes.local> (raw)
In-Reply-To: <43e72e890909031113r6010519br3b81d15cc331ba85@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
On Thu, 2009-09-03 at 11:13 -0700, Luis R. Rodriguez wrote:
> What I meant is it gobbles it up and spits another thing out. When it
> gobbles it up the routine then uses kref_put().
>
> > Why can it not track this?
>
> It probably can, just not sure if it follows kref_put(), I was under
> the impression here it doesn't and because of it we were getting false
> positives. Catalin, can you confirm?
Ah I'd think that if it can't track it then that's because we use a
pointer to the middle of the struct to keep track of it much of the
time.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-09-03 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1251958266-10692-1-git-send-email-lrodriguez@atheros.com>
[not found] ` <1251962791.3336.3.camel@johannes.local>
2009-09-03 18:13 ` Luis R. Rodriguez
2009-09-03 18:17 ` Johannes Berg [this message]
2009-09-03 20:43 ` Luis R. Rodriguez
2009-09-04 5:04 ` Johannes Berg
2009-09-04 8:25 ` Catalin Marinas
2009-09-04 21:21 ` Luis R. Rodriguez
2009-09-04 21:41 ` Luis R. Rodriguez
2009-09-04 21:58 ` Luis R. Rodriguez
2009-09-04 22:24 ` Catalin Marinas
2009-09-04 22:48 ` Luis R. Rodriguez
2009-09-05 0:03 ` Luis R. Rodriguez
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=1252001837.9336.2.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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 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®