From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Daniel Ritz <daniel.ritz@gmx.ch>
Cc: linux-pcmcia <linux-pcmcia@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] fix yenta memleak
Date: Sun, 28 Dec 2003 19:55:09 +0000 [thread overview]
Message-ID: <20031228195509.D20278@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200312281852.14336.daniel.ritz@gmx.ch>; from daniel.ritz@gmx.ch on Sun, Dec 28, 2003 at 06:52:14PM +0100
On Sun, Dec 28, 2003 at 06:52:14PM +0100, Daniel Ritz wrote:
> fix a memleak on yenta_socket unload.
> against 2.6.0
This looks fine; we don't allow the unload to continue until we've
made sure that sysfs has finished using sock, which prevents us
kfree'ing it while it's still in use.
I'll add this to the outgoing queue of pcmcia patches. Thanks.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
prev parent reply other threads:[~2003-12-28 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 17:52 [PATCH 2.6] fix yenta memleak Daniel Ritz
2003-12-28 19:55 ` Russell King [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=20031228195509.D20278@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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