From: Larry Finger <larry.finger@lwfinger.net>
To: netdev@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
"John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
dsd@gentoo.org
Cc: Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: Re: [PATCH] ieee80211softmac: Fix errors related to the work_struct changes
Date: Sun, 10 Dec 2006 22:24:27 -0600 [thread overview]
Message-ID: <457CDD7B.8080207@lwfinger.net> (raw)
In-Reply-To: <20061210173908.GB29871@p15091797.pureserver.info>
Ulrich Kunitz wrote:
> The signature of work functions changed recently from a context
> pointer to the work structure pointer. This caused a problem in
> the ieee80211softmac code, because the ieee80211softmac_assox_work
> function has been called directly with a parameter explicitly
> casted to (void*). This compiled correctly but resulted in a
> softlock, because mutex_lock was called with the wrong memory
> address. The patch fixes the problem. Another issue was a wrong
> call of the schedule_work function. Softmac works again and this
> fixes the problem I mentioned earlier in the zd1211rw rx tasklet
> patch. The patch is against Linus' tree (commit af1713e0).
>
> Signed-off-by: Ulrich Kunitz <kune@deine-taler.de>
Thanks Ulrich for this patch. I had spent the better part of 2 days bisecting Linus's git tree
trying to isolate the problem that kept the system from booting when my bcm43xx card was installed.
I thought that when someone _BROKE_ an interface with this kind of change, it was their duty to fix
_ALL_ parts of the system that uses this facility. At a minimum, shouldn't all maintainers get a
heads up? I don't subscribe to LKML, but I peruse the summary and I certainly do not recall seeing a
warning that this change was coming.
Larry
next prev parent reply other threads:[~2006-12-11 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 17:39 [PATCH] ieee80211softmac: Fix errors related to the work_struct changes Ulrich Kunitz
2006-12-10 17:49 ` Michael Buesch
2006-12-10 18:35 ` Ulrich Kunitz
2006-12-10 18:40 ` Michael Buesch
2006-12-10 18:40 ` Andrew Morton
2006-12-11 17:34 ` Larry Finger
2006-12-11 4:24 ` Larry Finger [this message]
2006-12-11 21:49 ` 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=457CDD7B.8080207@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=akpm@osdl.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=netdev@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).