From: Artem Bityutskiy <dedekind1@gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Sitsofe Wheeler <sitsofe@yahoo.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Christof Schmitt <christof.schmitt@de.ibm.com>
Subject: Re: [PULL] param sysfs oops (simple, leaky) fix, bool arrays fix
Date: Wed, 05 May 2010 10:25:14 +0300 [thread overview]
Message-ID: <1273044314.3702.98.camel@localhost> (raw)
In-Reply-To: <201005051503.42289.rusty@rustcorp.com.au>
On Wed, 2010-05-05 at 15:03 +0930, Rusty Russell wrote:
> On Wed, 5 May 2010 03:37:19 am Artem Bityutskiy wrote:
> > On Tue, 2010-05-04 at 11:53 +0930, Rusty Russell wrote:
> > > On Tue, 27 Apr 2010 08:23:24 pm Artem Bityutskiy wrote:
> > > > Rusty, correct me if I'm wrong, but it looks like the above memleak was
> > > > introduced by e180a6b7759a99a28cbcce3547c4c80822cb6c2a, where you added
> > > > the kstrdup(). So you kinda fixed the sysfs case (it still memleaks
> > > > though), but at the cost of additional insmod/rmmod leak, right?
> > >
> > > Yep!
> >
> > Are you working/planning to work on fixing this regression?
>
> I'm still ambivalent on it; I have patches but it's a lot of churn for not
> much gain.
>
> To fix this, we need a way to lock parameters against changing by sysfs, and
> we need to use it everywhere. Past experience has demonstrated that this will
> never be maintained.
>
> On the other hand, the leak is trivial.
Well, I am not very concerned with the "changing by sysfs" leak. This is
not a big deal, IMHO. I am concerned with the "rmmod" leak, which did
not exist before your patches, but exists now. People may do a lot of
insmod/rmmod, and on each rmmod they will loose this kstrdup-ed string.
I'll take a look at this tree, thank you.
> Here's a git tree if you want to look further:
>
> The following changes since commit 05ce7bfe547c9fa967d9cab6c37867a9cb6fb3fa:
> Linus Torvalds (1):
> Merge branch 'for_linus' of git://git.kernel.org/.../jack/linux-fs-2.6
>
> are available in the git repository at:
>
> git://git.kernel.org/rusty/linux-2.6-param-fixes.git master
Just in case others will clone, the correct URL seems to be
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-param-fixes.git master
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-05-05 7:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 22:32 [PULL] param sysfs oops (simple, leaky) fix, bool arrays fix Rusty Russell
2010-04-27 10:31 ` Artem Bityutskiy
2010-04-27 10:53 ` Artem Bityutskiy
2010-05-04 2:23 ` Rusty Russell
2010-05-04 18:07 ` Artem Bityutskiy
2010-05-05 5:33 ` Rusty Russell
2010-05-05 7:25 ` Artem Bityutskiy [this message]
2010-05-05 7:44 ` Takashi Iwai
2010-05-05 8:49 ` Artem Bityutskiy
2010-05-05 9:04 ` Artem Bityutskiy
2010-05-06 6:24 ` Takashi Iwai
2010-05-06 2:28 ` Rusty Russell
2010-06-22 16:50 ` Phil Carmody
2010-06-22 23:23 ` Rusty Russell
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=1273044314.3702.98.camel@localhost \
--to=dedekind1@gmail.com \
--cc=christof.schmitt@de.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sitsofe@yahoo.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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 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.