From: "John W. Linville" <linville@tuxdriver.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Arnaud Patard <apatard@mandriva.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH v2] Fix SLAB corruption during rmmod
Date: Wed, 18 Mar 2009 09:02:07 -0400 [thread overview]
Message-ID: <20090318130207.GA3527@tuxdriver.com> (raw)
In-Reply-To: <200903172256.35485.IvDoorn@gmail.com>
On Tue, Mar 17, 2009 at 10:56:35PM +0100, Ivo van Doorn wrote:
> On Tuesday 17 March 2009, John W. Linville wrote:
> > On Mon, Mar 16, 2009 at 08:24:27PM +0100, Ivo van Doorn wrote:
> > > At rmmod stage, the code path is the following one :
> > >=20
> > > rt2x00lib_remove_dev
> > > =A0 -> =A0rt2x00lib_uninitialize()
> > > =A0 =A0 =A0 =A0 -> rt2x00rfkill_unregister()
> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0-> rfkill_unregister()
> > > =A0 =A0 =A0 =A0 -> rt2x00rfkill_free()
> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0-> rfkill_free()
> > >=20
> > > The problem is that rfkill_free should not be called after rfkill=
_register
> > > otherwise put_device(&rfkill->dev) will be called 2 times. This p=
atch
> > > fixes this by only calling rt2x00rfkill_free() when rt2x00rfkill_=
register()
> > > hasn't been called or has failed.
> > >=20
> > > Signed-off-by: Gertjan van Wingerde <gwingerde@gmail.com>
> > > Tested-by: Arnaud Patard <apatard@mandriva.com>
> > > Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
> > >=20
> > > ---
> > > John, this patch is for 2.6.29 and only 2.6.29 since rfkill suppo=
rt itself
> > > was removed from later versions (replaced by input_polldev).
> > > The patch is quite big to be merged in a late state of the releas=
e cycle,
> > > but since the SLAB corruption is a serious problem, I hope this c=
an get in regardless.
> >=20
> > Could you send me a version of this that applies on top of
> > wireless-testing?
>=20
> Actually no, the code isn't present at all in wireless-testing.
> As I said, after 2.6.29 the entire rfkill structure is removed from r=
t2x00
> and replaced by input_polldev.
I guess I misunderstood. So just to be clear, no remnant or shadow
of this patch should live-on to 2.6.30?
It's just that the merge conflicts created by this patch were awful.
With 2.6.29's release presumably close, maybe this is a candidate
for the stable tree?
John
--=20
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-18 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 18:25 [PATCH] Fix SLAB corruption during Ivo van Doorn
2009-03-16 19:15 ` Dan Williams
2009-03-16 19:21 ` Ivo van Doorn
2009-03-16 19:24 ` [PATCH v2] Fix SLAB corruption during rmmod Ivo van Doorn
2009-03-17 21:13 ` John W. Linville
2009-03-17 21:56 ` Ivo van Doorn
2009-03-18 13:02 ` John W. Linville [this message]
2009-03-18 13:32 ` Ivo van Doorn
2009-03-18 21:37 ` John W. Linville
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=20090318130207.GA3527@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=apatard@mandriva.com \
--cc=dcbw@redhat.com \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@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).