linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qca.qualcomm.com>
Subject: Re: [PATCH 5/7] ath6kl: convert ath6kl_info/err/warn macros to real functions
Date: Thu, 27 Dec 2012 17:55:46 +0200	[thread overview]
Message-ID: <87wqw3ebgd.fsf@qca.qualcomm.com> (raw)
In-Reply-To: <871uebfqe3.fsf@qca.qualcomm.com> (Kalle Valo's message of "Thu, 27 Dec 2012 17:47:48 +0200")

Kalle Valo <kvalo@qca.qualcomm.com> writes:

>> Note that by inserting the tracing here later, you're relying on the
>> fact that "%pV" does va_copy(). This isn't true in all kernel versions,
>> I think there's on version or so where %pV is supported but didn't
>> va_copy(). That may lead to problems (I don't remember what kind) here.
>>
>> This is relevant for compat only, I think I carry a patch there to add
>> va_copy() into the tracing or something.
>
> Compat-drivers has 55-iwlwifi-msg-trace-fix.patch which says:
>
> "In recent kernels, %pV will copy the va_list before using it.
> This isn't true for all kernels, so copy the va_list for use
> by the dev_*() functions, otherwise the kernel will crash if
> the message is printed and traced."
>
> I take it that the problem happens when the message is both printed and
> traced at the same time. So ath6kl will need a similar patch as well.

For the archives: I'm guessing this is the commit which fixed the issue:

commit 5756b76e4db643d8f75174a9a50038523d4b9e32
Author: Jan Beulich <JBeulich@suse.com>
Date:   Mon Mar 5 16:49:24 2012 +0000

    vsprintf: make %pV handling compatible with kasprintf()

And git-describe tells me that it was introduced in 3.3-rc7, so quite
recent.

Kalle

  reply	other threads:[~2012-12-27 15:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27 11:44 [PATCH 0/7] ath6kl: tracing support Kalle Valo
2012-12-27 11:44 ` [PATCH 1/7] ath6kl: add tracing support and tracing points for wmi packets Kalle Valo
2012-12-27 11:44 ` [PATCH 2/7] ath6kl: add tracing points for sdio transfers Kalle Valo
2012-12-27 12:13   ` Johannes Berg
2012-12-27 15:32     ` Kalle Valo
2012-12-27 11:44 ` [PATCH 3/7] ath6kl: add tracing point for hif irqs Kalle Valo
2012-12-27 11:44 ` [PATCH 4/7] ath6kl: adding tracing points for htc_mbox Kalle Valo
2012-12-27 11:44 ` [PATCH 5/7] ath6kl: convert ath6kl_info/err/warn macros to real functions Kalle Valo
2012-12-27 12:19   ` Johannes Berg
2012-12-27 15:47     ` Kalle Valo
2012-12-27 15:55       ` Kalle Valo [this message]
2012-12-27 11:44 ` [PATCH 6/7] ath6kl: add tracing support to log functions Kalle Valo
2012-12-27 11:44 ` [PATCH 7/7] ath6kl: add tracing support to debug message macros Kalle Valo

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=87wqw3ebgd.fsf@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qca.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --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).