public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Christoph Lameter <cl@linux.com>
Cc: penberg@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] slub: Enable backtrace for create/delete points.
Date: Fri, 01 Jul 2011 07:20:21 -0700	[thread overview]
Message-ID: <4E0DD7A5.7020106@candelatech.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1107010905350.2458@router.home>

On 07/01/2011 07:08 AM, Christoph Lameter wrote:
> On Tue, 28 Jun 2011, greearb@candelatech.com wrote:
>
>> diff --git a/mm/slub.c b/mm/slub.c
>> index 35f351f..3477ce5 100644
>> --- a/mm/slub.c
>> +++ b/mm/slub.c
>> @@ -191,8 +191,12 @@ static LIST_HEAD(slab_caches);
>>   /*
>>    * Tracking user of a slab.
>>    */
>> +#define TRACK_ADDRS_COUNT 16
>>   struct track {
>> -	unsigned long addr;	/* Called from address */
>> +	unsigned long caddr;
>
> Keep the name the same since its role does not change. That makes the
> patch touch less code.
>
>> +#ifdef CONFIG_STACKTRACE
>> +	unsigned long addrs[TRACK_ADDRS_COUNT];	/* Called from address */
>> +#endif
>>   	int cpu;		/* Was running on cpu */
>>   	int pid;		/* Pid context */
>>   	unsigned long when;	/* When did the operation occur */
>> @@ -420,7 +424,25 @@ static void set_track(struct kmem_cache *s, void *object,
>>   	struct track *p = get_track(s, object, alloc);
>>
>>   	if (addr) {
>> -		p->addr = addr;
>> +#ifdef CONFIG_STACKTRACE
>> +		struct stack_trace trace;
>> +		int i;
>> +
>> +		trace.nr_entries = 0;
>> +		trace.max_entries = TRACK_ADDRS_COUNT;
>> +		trace.entries = p->addrs;
>> +		trace.skip = 3;
>> +		save_stack_trace(&trace);
>> +
>> +		/* See rant in lockdep.c */
>> +		if (trace.nr_entries != 0&&
>> +		    trace.entries[trace.nr_entries - 1] == ULONG_MAX)
>> +			trace.nr_entries--;
>> +
>> +		for (i = trace.nr_entries; i<  TRACK_ADDRS_COUNT; i++)
>> +			p->addrs[i] = 0;
>> +#endif
>
> Hmmm... Is this really working on all architectures? I remember from years
> past that we had issues with adding the same functionality to slab.

The lockdep code seems to use the same basic logic, and I didn't notice
any arch checks in it.  I think recently someone must have fixed the backtrace
logic to be more easily used...this API didn't exist a few kernels
ago.

>
> Otherwise the patch is quite straightforward (and it will be much cleaner
> if you do not change the name of "addr").

Ok, will change that.

Thanks,
Ben

>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2011-07-01 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  0:47 [PATCH v2 0/2] SLUB memory debugging improvements greearb
2011-06-29  0:47 ` [PATCH v2 1/2] slub: Enable backtrace for create/delete points greearb
2011-07-01 14:08   ` Christoph Lameter
2011-07-01 14:20     ` Ben Greear [this message]
2011-06-29  0:47 ` [PATCH v2 2/2] slub: Add method to verify memory is not freed greearb
2011-07-01 14:11   ` Christoph Lameter
2011-07-01 14:23     ` Ben Greear
2011-07-07 18:00     ` Ben Greear

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=4E0DD7A5.7020106@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@kernel.org \
    /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