From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Santiago Carot Nemesio <scarot@libresoft.es>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 3/3] SDP
Date: Tue, 27 Apr 2010 17:50:22 +0200 [thread overview]
Message-ID: <1272383422.22838.151.camel@localhost.localdomain> (raw)
In-Reply-To: <20100427150516.GA11895@jh-x301>
Hi Johan,
> > This patch add memory checks after malloc function is called.
> >
> > >From 7cce3be5a1a1d506f4da71fc394ee3ccf71d8159 Mon Sep 17 00:00:00 2001
> > From: Santiago Carot Nemesio <sancane@gmail.com>
> > Date: Tue, 27 Apr 2010 15:19:44 +0200
> > Subject: [PATCH 3/3] Added memory checks
> >
> >
> > Signed-off-by: Santiago Carot Nemesio <sancane@gmail.com>
not signed-off-by in BlueZ please. That is a kernel requirement.
> I've pushed the first two patches upstream but I did have to fix their
> commit messages before that. If you try "git am" yourself for what you
> sent you'll see that the summary line becomes just "SDP" for all of them
> and it should be more descriptive than that (for examples see the bluez
> commit history).
>
> The third patch should also see these changes but additionally there
> were a few issues I noticed in the actual code:
>
> > u = malloc(sizeof(uuid_t));
> > + if (!u) {
> > + errno = ENOMEM;
> > + goto fail;
> > + }
>
> malloc will set the errno for you on failure so you shouldn't need to do
> it in your code.
>
> > lang = malloc(sizeof(sdp_lang_attr_t));
> > + if (!lang) {
> > + errno = ENOMEM;
> > + goto fail;
>
> Same here.
>
> > - uuid_t *uuid128 = bt_malloc(sizeof(uuid_t));
> > + uuid_t *uuid128 = malloc(sizeof(uuid_t));
>
> This seems unrelated to the other changes in the patch. I don't know the
> exact philosophy of when bt_malloc should be used and when malloc should
> be used (maybe Marcel can comment on that), but I'd simply leave this
> change out of the patch.
Since you are suppose to use bt_free to free the memory, you also should
allocate it with bt_malloc. They are simple wrappers, but important to
make sure all library allocation and freeing is done with the same
function. Not free() or malloc() from library A against another one form
library B.
In most cases this makes no difference, but there are corner cases where
is does make a difference. So please keep bt_malloc() if the memory
needs to be freed by the application.
Regards
Marcel
next prev parent reply other threads:[~2010-04-27 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 13:34 [PATCH 1/3] SDP Santiago Carot Nemesio
2010-04-27 13:37 ` [PATCH 2/3] SDP Santiago Carot Nemesio
2010-04-27 13:39 ` [PATCH 3/3] SDP Santiago Carot Nemesio
2010-04-27 13:51 ` SDP comments Santiago Carot Nemesio
2010-04-27 15:07 ` Johan Hedberg
2010-04-27 15:05 ` [PATCH 3/3] SDP Johan Hedberg
2010-04-27 15:50 ` Marcel Holtmann [this message]
2010-04-27 15:59 ` Santiago Carot Nemesio
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=1272383422.22838.151.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=scarot@libresoft.es \
/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).