All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2.6] 7/7 replace snd_kmalloc_strdup by kstrdup
Date: Tue, 01 Feb 2005 14:16:26 +0100	[thread overview]
Message-ID: <s5hvf9cfmj9.wl@alsa2.suse.de> (raw)
In-Reply-To: <41FF7F0D.5080800@grupopie.com>

At Tue, 01 Feb 2005 13:07:25 +0000,
Paulo Marques wrote:
> 
> I thought of going all the way and changing the callers of kstrdup in 
> sound to use kfree, so that it would work without debugging memory 
> allocated for strdup'ed strings.
> 
> However the code there already uses kfree, just not the standard kfree 
> because it might have been defined to something else in core.h if 
> CONFIG_SND_DEBUG_MEMORY is set.
> 
> We could still go all the way and carry on with this approach: use the 
> standard kstrdup / kfree when not CONFIG_SND_DEBUG_MEMORY, and define 
> kstrdup to be an internal sound function in sound/core/memory.c when 
> CONFIG_SND_DEBUG_MEMORY is set.

This sounds good.  We can do just like normal kmalloc:

#ifdef CONFIG_SND_DEBUG_MEMORY
...
#define kstrdup(s) my_kstrdup_wrapper(s)
#endif

> Do you prefer that I do another patch to do this, or that I just drop 
> the patch and leave snd_kmalloc_strdup alone?

Heh, it's up to you ;)  Using kstrdup() in normal cases would be
better, of course.


Takashi

  parent reply	other threads:[~2005-02-01 13:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  3:28 [PATCH 2.6] 7/7 replace snd_kmalloc_strdup by kstrdup pmarques
2005-02-01 11:17 ` Takashi Iwai
2005-02-01 12:27   ` Paulo Marques
2005-02-01 12:32     ` Takashi Iwai
2005-02-01 13:07       ` Paulo Marques
2005-02-01 13:16         ` Takashi Iwai
2005-02-01 13:16         ` Takashi Iwai [this message]
2005-02-01 15:39           ` Paulo Marques
2005-02-01 16:39             ` Takashi Iwai
2005-02-01 17:15               ` Paulo Marques
2005-02-02 11:29                 ` Takashi Iwai
2005-02-02 11:29                   ` Takashi Iwai
2005-02-01 16:39             ` Takashi Iwai
2005-02-01 12:32     ` Takashi Iwai
2005-02-01 11:17 ` Takashi Iwai
2005-02-01 11:17 ` Takashi Iwai

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=s5hvf9cfmj9.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.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.