From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pavel Roskin <proski@gnu.org>, Markus Baier <markus_baier@web.de>,
linux-wireless@vger.kernel.org, kalle.valo@iki.fi
Subject: Re: Starting hostapd causes kernel panic
Date: Sat, 23 Jan 2010 13:53:14 -0800 [thread overview]
Message-ID: <4B5B6FCA.2070900@redfish-solutions.com> (raw)
In-Reply-To: <1264251576.2593.30.camel@johannes.local>
On 01/23/2010 04:59 AM, Johannes Berg wrote:
> On Fri, 2010-01-22 at 17:06 -0500, Pavel Roskin wrote:
>
>> On Fri, 2010-01-22 at 22:53 +0100, Johannes Berg wrote:
>>
>>>> I assume it's another case where tx->key should be checked for being
>>>> NULL. In fact, it's set to NULL on the preceding line!
>>>>
>>> or an else inserted.
>>>
>> Whatever you prefer. Either way, the panic is fixed now!
>>
> Great, and sorry about that! I'll send a patch to insert the else too.
>
> johannes
>
Did you send that patch? I'd like to apply it. Please copy me when you send it out.
Thanks.
next prev parent reply other threads:[~2010-01-23 21:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 20:14 Starting hostapd causes kernel panic Markus Baier
2010-01-22 20:23 ` pat-lkml
2010-01-22 20:59 ` Markus Baier
2010-01-22 20:28 ` Johannes Berg
2010-01-22 22:45 ` Markus Baier
2010-01-22 20:53 ` Johannes Berg
2010-01-22 21:42 ` Pavel Roskin
2010-01-22 21:50 ` Markus Baier
2010-01-22 21:53 ` Johannes Berg
2010-01-22 22:06 ` Pavel Roskin
2010-01-23 12:59 ` Johannes Berg
2010-01-23 21:53 ` Philip A. Prindeville [this message]
2010-01-24 5:58 ` Kalle Valo
2010-01-24 8:14 ` Philip A. Prindeville
2010-01-24 8:27 ` Kalle Valo
2010-01-24 11:42 ` Johannes Berg
2010-01-24 21:07 ` Philip A. Prindeville
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=4B5B6FCA.2070900@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=markus_baier@web.de \
--cc=proski@gnu.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).