From: "Kay Sievers" <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udevd: fix memory leak
Date: Thu, 23 Oct 2008 09:34:16 +0000 [thread overview]
Message-ID: <ac3eb2510810230234u7a9ce3bcxb71abc6a488fed4b@mail.gmail.com> (raw)
In-Reply-To: <49004388.1050705@tuffmail.co.uk>
On Thu, Oct 23, 2008 at 11:27, Alan Jenkins <alan-jenkins@tuffmail.co.uk> wrote:
> Re: b99028c96307e729303be8f6750418979a7488b9 shrink struct udev_event
> --- a/udev/udev-rules.c
> +++ b/udev/udev-rules.c
> @@ -1970,6 +1970,7 @@ int udev_rules_apply_to_event(struct udev_rules *rules, struct udev_event *event
> count = util_replace_chars(name_str, ALLOWED_CHARS_FILE);
> if (count > 0)
> info(event->udev, "%i character(s) replaced\n", count);
> + free(event->name);
> event->name = strdup(name_str);
> }
> break;
Applied.
Thanks,
Kay
prev parent reply other threads:[~2008-10-23 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 9:27 [PATCH] udevd: fix memory leak Alan Jenkins
2008-10-23 9:34 ` Kay Sievers [this message]
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=ac3eb2510810230234u7a9ce3bcxb71abc6a488fed4b@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.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;
as well as URLs for NNTP newsgroup(s).