From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Steve deRosier <derosier@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: ath6kl: assure headroom of skbuff is writable in .start_xmit()
Date: Wed, 26 Apr 2017 08:53:37 +0000 (UTC) [thread overview]
Message-ID: <20170426085337.181AA61493@smtp.codeaurora.org> (raw)
In-Reply-To: <1493111408-27692-1-git-send-email-arend.vanspriel@broadcom.com>
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.
--
https://patchwork.kernel.org/patch/9697757/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-04-26 8:53 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 [this message]
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
[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=20170426085337.181AA61493@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=derosier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.