linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Steve deRosier <derosier@gmail.com>
Cc: James Hughes <james.hughes@raspberrypi.org>,
	Arend Van Spriel <arend.vanspriel@broadcom.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath6kl: assure headroom of skbuff is writable in .start_xmit()
Date: Thu, 4 May 2017 13:08:17 +0000	[thread overview]
Message-ID: <87o9v8rcqn.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CALLGbRJ=xWGBvWzj=SjfeHPV_c43JEaDbUNmP7=0g2=py0U=vQ@mail.gmail.com>       (Steve deRosier's message of "Wed, 26 Apr 2017 21:55:48 -0700")

Steve deRosier <derosier@gmail.com> writes:

> On Wed, Apr 26, 2017 at 12:54 PM, James Hughes
> <james.hughes@raspberrypi.org> wrote:
>> On 26 April 2017 at 19:03, Arend Van Spriel
>> <arend.vanspriel@broadcom.com> wrote:
>>>
>>>
>>> On 26-4-2017 17:44, Steve deRosier wrote:
>>>> On Wed, Apr 26, 2017 at 1:53 AM, Kalle Valo <kvalo@codeaurora.org> wro=
te:
>>>>> Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:
>>>>>> An issue was found brcmfmac driver in which a skbuff in .start_xmit(=
)
>>>>>> callback was actually cloned. So instead of checking for sufficient
>>>>>> headroom it should also be writable. Hence use skb_cow_head() to
>>>>>> check and expand the headroom appropriately.
>>>>>>
>>>>>> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
>>>>>
>>>>> Steve, would you have time to run a quick test with this?
>>>>>
>>>>> Patch set to Deferred.
>>>>>
>>>>
>>>> Happy to give it a quick spin on both of my platforms.
>>>>
>
> @ Arend and James, thanks for the info. I understand it, but
> unfortunately I can't seem to replicate the problems on my platforms
> with the limited time I have available to test it. It also may have to
> do with my platforms having special custom bridging related code, or
> just me having setup too simple of a test.
>
> That said...
>
> @Kalle: I have tested on both my 6004 and 6003 platforms. I didn't
> notice any incorrect behavior in my testing. But I don't have a test
> setup that would have shown the original problem as reported on the
> brcm driver so I can't say that the change actually _fixes_ anything.
> Only that in my testing it doesn't seem to break anything.
>
> Tested-by: Steve deRosier <derosier@gmail.com>

Yeah, I was mostly worried about regression. I didn't expect you to
replicate the bug. Thanks for testing, I'll add this patch to my queue.

--=20
Kalle Valo=

  parent reply	other threads:[~2017-05-04 13:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25  9:10 [PATCH] ath6kl: assure headroom of skbuff is writable in .start_xmit() Arend van Spriel
2017-04-25  9:36 ` James Hughes
2017-04-25 11:10   ` Arend Van Spriel
2017-04-25 11:50     ` James Hughes
2017-04-26  8:53 ` Kalle Valo
2017-04-26 15:44   ` Steve deRosier
2017-04-26 18:03     ` Arend Van Spriel
2017-04-26 19:54       ` James Hughes
2017-04-27  4:55         ` Steve deRosier
2017-04-27  8:54           ` James Hughes
2017-05-04 13:08           ` Kalle Valo [this message]
     [not found] ` <20170426085337.293296148E@smtp.codeaurora.org>
2017-04-26  9:00   ` Arend van Spriel
2017-05-19  7:48 ` 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=87o9v8rcqn.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=derosier@gmail.com \
    --cc=james.hughes@raspberrypi.org \
    --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).