Depending on the preempt mode, the bpf_prog stored in xdp_prog may be
freed despite the use of call_rcu inside bpf_prog_put. The situation is
possible when running in PREEMPT_RCU=y mode, for instance, since the rcu
callback for destroying the bpf prog can run even during the bh handling
in the mlx4
Hi All,
On Mon, Aug 8, 2016 at 5:39 PM, Christophe JAILLET
wrote:
> This patch should be a no-op. It just simplifies code by using the name of
> a variable instead of its type when calling 'sizeof'.
>
> Signed-off-by: Christophe JAILLET
Reviewed-by: Julian Calaby
Thanks,
--
Julian Calaby
E
> > Hmm, I didn't see where this code got moved to...
>
>Ah, it's the duplicated code... you should've either explicitly
> stated that in the change log or done this in a separate patch, I
> think.
Hi Sergei
Maybe you should read the comments I made :-)
Andrew
Hi All,
On Tue, Aug 30, 2016 at 3:05 AM, Joe Perches wrote:
> Correct some trivial comment typos.
> Remove unnecessary parentheses in a long line.
> Convert a return; before the end of a void function definition to just ;
>
> Signed-off-by: Joe Perches
This all looks correct to me. I wish you'd
Hi All,
On Sun, Sep 4, 2016 at 2:43 AM, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistakes in dev_dbg message.
>
> Signed-off-by: Colin Ian King
Reviewed-by: Julian Calaby
Thanks,
--
Julian Calaby
Email: julian.cal...@gmail.com
Profile: http://www.google.com/pro
I asked on 2016-06-07 17:19:43 [-0700]:
>>cpsw_rx_poll() is called even when there is essentially no network
>>traffic, so I'm not sure how to tell if NAPI is working as intended.
On Thu, Jun 9, 2016 at 5:37 AM, Sebastian Andrzej Siewior
wrote:
> You should see an invocation of __raise_softirq_i
On 09/01/2016 11:15 PM, Jeremy Linton wrote:
Move phy startup/shutdown into the smsc911x_open/stop routines. This
allows the module to be unloaded because phy_connect_direct is no longer
always holding the module use count. This one change also resolves a
number of other problems.
The link stat
On 09/03/2016 10:23 PM, Sergei Shtylyov wrote:
The /proc/irq/xx information is incorrect for smsc911x because
the request_irq is happening before the register_netdev has the
proper device name. Moving it to the open also fixes the case
of when the device is renamed.
Reported-by: Will Deacon
Si
On 09/01/2016 11:15 PM, Jeremy Linton wrote:
The /proc/irq/xx information is incorrect for smsc911x because
the request_irq is happening before the register_netdev has the
proper device name. Moving it to the open also fixes the case
of when the device is renamed.
Reported-by: Will Deacon
Sign
Bjorn Andersson wrote:
> Some firmware versions sends a "print register indication", handle this
> by printing out the content.
>
> Cc: Nicolas Dechesne
> Signed-off-by: Bjorn Andersson
This doesn't apply anymore, please rebase.
--
Sent by pwcli
https://patchwork.kernel.org/patch/9208737/
Giedrius Statkevi?ius wrote:
> A regression was introduced in commit id 79d4db1214a ("ath9k: cleanup
> led_pin initial") that broken the WLAN status led on my laptop with
> AR9287 after suspending and resuming.
>
> Steps to reproduce:
> * Suspend (laptop)
> * Resume (laptop)
> * Observe that the
Pravin,
Thanks for the feedback. Some replies below.
Thanks.
Eric.
On Fri, Sep 02, 2016 at 02:42:30PM -0700, pravin shelar wrote:
> On Thu, Sep 1, 2016 at 1:45 PM, Eric Garver wrote:
> > Add support for 802.1ad including the ability to push and pop double
> > tagged vlans. Add support for 802.1
Nicolas Iooss wrote:
> The struct cfg80211_pmksa defines its bssid field as:
>
> const u8 *bssid;
>
> contrary to struct brcmf_pmksa, which uses:
>
> u8 bssid[ETH_ALEN];
>
> Therefore in brcmf_cfg80211_del_pmksa(), &pmksa->bssid takes the address
> of this field (of type u8**), not the
Colin Ian King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_err message.
>
> Signed-off-by: Colin Ian King
> Reviewed-by: Julian Calaby
Thanks, 1 patch applied to wireless-drivers-next.git:
b46b599328e6 zd1211rw: fix spelling mistake "firmeware" -> "firmware"
--
On Fri, 2 Sep 2016 11:09:23 -0700 (PDT) Linus Torvalds
wrote:
> From: Linus Torvalds
> Date: Thu, 1 Sep 2016 14:56:49 -0700
> Subject: [PATCH 1/2] Revert "af_unix: Fix splice-bind deadlock"
>
> This reverts commit c845acb324aa85a39650a14e7696982ceea75dc1.
>
> It turns out that it just replaces
From: Colin Ian King
Trivial fix to spelling mistakes in dev_dbg message.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
b/dri
From: Colin Ian King
caldata is not being free'd on the error exit path, causing
a memory leak and data definitely should not be freed. Free
caldata instead of data.
Thanks to Kalle Valo for spotting that data should not be
free'd.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/ath/at
On 02/09/16 16:45, Valo, Kalle wrote:
> Colin King writes:
>
>> From: Colin Ian King
>>
>> caldata is not being free'd on the error exit path, causing
>> a memory leak. kfree it to fix the leak.
>>
>> Signed-off-by: Colin Ian King
>> ---
>> drivers/net/wireless/ath/ath10k/pci.c | 1 +
>> 1 fil
Some more users complaining about this:
https://bbs.archlinux.org/viewtopic.php?id=215978
On Thu, Sep 01, 2016 at 08:47:02PM +0300, Giedrius Statkevičius wrote:
> A regression was introduced in commit id 79d4db1214a ("ath9k: cleanup
> led_pin initial") that broken the WLAN status led on my laptop
On Fri, Sep 02, 2016 at 02:42:41PM -0700, pravin shelar wrote:
> On Thu, Sep 1, 2016 at 1:45 PM, Eric Garver wrote:
> > With 802.1ad support these are parsed and set upfront by
> > parse_vlan_from_nlattrs() before ovs_key_from_nlattrs() is ever called.
> > As such we should never see a VLAN attrib
From: Zhu Yanjun
The struct nlattr variable should not be changed.
Signed-off-by: Zhu Yanjun
---
drivers/net/vxlan.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
index f605a36..ce65897 100644
--- a/drivers/net/vxlan.c
+++ b/d
Hello,
While running syzkaller fuzzer I've got the following report:
BUG: KASAN: stack-out-of-bounds in sixpack_receive_buf+0xf8a/0x1450 at
addr 880037fbf850
Read of size 1 by task syz-executor/6759
page:eadfefc0 count:0 mapcount:0 mapping: (null) index:0x0
flags: 0x1fffc
Hello,
While running syzkaller fuzzer I've got the following report:
BUG: KASAN: stack-out-of-bounds in sixpack_receive_buf+0xf8a/0x1450 at
addr 880037fbf850
Read of size 1 by task syz-executor/6759
page:eadfefc0 count:0 mapcount:0 mapping: (null) index:0x0
flags: 0x1fffc
Kalle Valo writes:
> Baoyou Xie wrote:
>> We get 1 warning about global functions without a declaration
>> in the rtl8xxxu rtl8xxxu_core.c when building with W=1:
>> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c:898:1:
>> warning: no previous prototype for 'rtl8xxxu_gen1_h2c_cmd'
>> [-Wmi
From: Gao Feng
When memory is exhausted, nfct_seqadj_ext_add may fail to add the seqadj
extension. But the function nf_ct_seqadj_init doesn't check if get valid
seqadj pointer by the nfct_seqadj, while other functions perform the
sanity check.
So the system would be panic when nfct_seqadj_ext_ad
On Tue, Mar 22, 2016 at 1:32 PM, Dmitry Vyukov wrote:
> On Tue, Mar 22, 2016 at 9:09 AM, Jiri Slaby wrote:
>> On 03/21/2016, 04:58 PM, Jiri Slaby wrote:
>>> Hello,
>>>
>>> On 03/18/2016, 09:52 PM, Tejun Heo wrote:
On Thu, Mar 17, 2016 at 01:00:13PM +0100, Jiri Slaby wrote:
>>> I have not
Javier Martinez Canillas wrote:
> If request_irq() fails in mwifiex_sdio_probe_of(), only an error message
> is printed but the actual error is not propagated to the caller function.
>
> Signed-off-by: Javier Martinez Canillas
What's the conclusion with this patch? Should I drop it or take it?
Baoyou Xie wrote:
> We get 1 warning about global functions without a declaration
> in the rtl8xxxu rtl8xxxu_core.c when building with W=1:
> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c:898:1: warning: no
> previous prototype for 'rtl8xxxu_gen1_h2c_cmd' [-Wmissing-prototypes]
>
> In fa
Baoyou Xie wrote:
> We get 1 warning when building kernel with W=1:
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/tracepoint.c:23:6: warning:
> no previous prototype for '__brcmf_err' [-Wmissing-prototypes]
>
> In fact, this function is declared in brcmfmac/debug.h, so this patch
> adds
Heinrich Schuchardt wrote:
> for_each_property_of_node is only executed if the
> property prop is not NULL.
>
> Signed-off-by: Heinrich Schuchardt
> Acked-by: Amitkumar Karwar
Thanks, 1 patch applied to wireless-drivers-next.git:
2f69e67058fb mwifiex: remove superfluous condition
--
Sent by
Heinrich Schuchardt wrote:
> We are using mac as source address in a memcpy.
> In the lines below we can assume mac is not NULL.
>
> Signed-off-by: Heinrich Schuchardt
> Acked-by: Amitkumar Karwar
Thanks, 1 patch applied to wireless-drivers-next.git:
b0d80f19c14f mwifiex: key_material_v2 remo
Colin Ian King wrote:
> From: Colin Ian King
>
> The IEEE80211_STYPE_ACTION case is missing a break in the switch
> statement, causing it to fall through to the default case that
> reports a debug message about an unknown frame subtype. Fix this
> by adding in the missing break statement.
>
> S
Christophe Jaillet wrote:
> In 'mwifiex_get_ver_ext', we have:
>struct mwifiex_ver_ext ver_ext;
>
>memset(&ver_ext, 0, sizeof(struct host_cmd_ds_version_ext));
>
> This is likely that memset'ing sizeof(struct mwifiex_ver_ext) was expected.
> Remove the ambiguity by using the variable nam
Heinrich Schuchardt wrote:
> If sta == NULL, the changed line will not be reached.
> So no need to check that sta != NULL here.
>
> Signed-off-by: Heinrich Schuchardt
> Acked-by: Larry Finger
Thanks, 1 patch applied to wireless-drivers-next.git:
f898005ff99f rtlwifi: remove superfluous condit
Pavel Andrianov wrote:
> Likely wl3501_reset should acquire spinlock as wl3501_{open, close}.
> One of calls of wl3501_reset has been already protected.
> The others were unprotected and might lead to a race condition.
> The patch adds spinlock into the wl3501_reset and removes it from
> wl3501_t
From: Sean Wang
The patch adds support for aggregating more SKBs feed into NAPI in
order to get more benefits from generic receive offload (GRO) by
peeking at the RX ring status and moving more packets right before
returning from NAPI RX polling handler if NAPI budgets are still
available and som
From: Sean Wang
The patch makes move wmb() to outside the loop that could help
RX path handling more faster although that RX descriptors aren't
freed for DMA to use as soon as possible, but based on my experiment
and the result shows it still can reach about 943Mbpis without
performance drop that
From: Sean Wang
Changes since v1:
- fix message typos and add coverletter
Changes since v2:
- split from the previous series for submitting add enhancements as
a series targeting 'net-next' and add indents before comments.
Changes since v3:
- merge the patch using PDMA RX path
- fixed the in
Fri, Sep 02, 2016 at 08:49:34PM CEST, john.fastab...@gmail.com wrote:
>On 16-09-02 10:18 AM, Florian Fainelli wrote:
>> Hi all,
>>
>
>Hi Florian,
>
>> (apologies for the long CC list and the fact that I can't type correctly
>> email addresses)
>>
>
>My favorite topic ;)
>
>> While working on addi
39 matches
Mail list logo
