The values represented by qede->flags is being used in mixed ways:
1. As 'value' at some places e.g., QEDE_FLAGS_IS_VF usage
2. As bit-mask(value) at some places e.g., QEDE_FLAGS_PTP_TX_IN_PRORGESS
usage.
This implementation pose problems in future when we want to add more flag
values e.g.
The patch adds driver support for MBI image update through MFW.
Signed-off-by: Sudarsana Reddy Kalluru
Signed-off-by: Ariel Elior
Signed-off-by: Michal Kalderon
---
drivers/net/ethernet/qlogic/qed/qed_hsi.h | 6
drivers/net/ethernet/qlogic/qed/qed_main.c | 13 +++--
drivers/net/ethe
In the case of internal reload (e.g., mtu change), there could be a race
between link-up notification from mfw and the driver unload processing. In
such case kernel assumes the link is up and starts using the queues which
leads to the server crash.
Send link notification to the kernel only when dr
MFW sends UFP notifications mostly during the device init phase and PFs
might not be assigned with a name by this time. Hence capturing port-id in
the debug messages would help in finding which PF the ufp notification was
sent to.
Also, fixed a minor scemantic issue in a debug print.
Signed-off-b
From: Sudarsana Reddy Kalluru
The patch series add few enhancements to qed/qede drivers.
Changes from previous versions:
---
v2: Use __set_bit()/__clear_bit() where data access doesn't need to be
atomic.
Please consider applying it to "net-next".
Sudarsana Reddy
From: David Ahern
Date: Thu, 22 Nov 2018 09:51:27 -0700
> I would like to see basic packets, bytes, and dropped counters tracked
> for Rx and Tx via the standard netdev counters for all devices. This is
> for ease in accounting as well as speed and simplicity for bumping
> counters for virtual de
1) Need to take mutex in ath9k_add_interface(), from Dan Carpenter.
2) Fix mt76 build without CONFIG_LEDS_CLASS, from Arnd Bergmann.
3) Fix socket wmem accounting in SCTP, from Xin Long.
4) Fix failed resume crash in ena driver, from Arthur Kiyanovski.
5) qed driver passes bytes instead of bi
Kernel commit 48872c11b772 ("net_sched: sch_fq: add dctcp-like marking")
added support for TCA_FQ_CE_THRESHOLD attribute.
This patch adds iproute2 support for it.
It also makes sure fq_print_xstats() can deal with smaller tc_fq_qd_stats
structures given by older kernels.
Usage :
FQATTRS="ce_thr
From: Linus Walleij
Date: Sat, 24 Nov 2018 00:16:34 +0100
> From: Andreas Fiedler
>
> The TX stats should be started with the tx_stats_syncp,
> there seems to be a copy/paste error in the driver.
>
> Signed-off-by: Andreas Fiedler
> Signed-off-by: Linus Walleij
Applied.
From: Quentin Schulz
Date: Fri, 23 Nov 2018 19:01:51 +0100
> The vsc85xx_default_config function called in the vsc85xx_config_init
> function which is used by VSC8530, VSC8531, VSC8540 and VSC8541 PHYs
> mistakenly calls phy_read and phy_write in-between phy_select_page and
> phy_restore_page.
>
From: Fabio Estevam
Date: Fri, 23 Nov 2018 15:46:50 -0200
> The correct form is "can be probed", so fix the typo.
>
> Signed-off-by: Fabio Estevam
Applied.
From: Lorenzo Bianconi
Date: Fri, 23 Nov 2018 18:28:01 +0100
> Reset snd_queue tso_hdrs pointer to NULL in nicvf_free_snd_queue routine
> since it is used to check if tso dma descriptor queue has been previously
> allocated. The issue can be triggered with the following reproducer:
>
> $ip link
From: Claudiu Manoil
Date: Fri, 23 Nov 2018 12:46:00 +0200
> +static int enetc_poll(struct napi_struct *napi, int budget)
> +{
> + struct enetc_int_vector
> + *v = container_of(napi, struct enetc_int_vector, napi);
> + bool complete = true;
> + int work_done;
> + int i
From: "Onnasch, Alexander (EXT)"
Date: Fri, 23 Nov 2018 09:36:11 +
> With Micrel KSZ8061 PHY, the link may occasionally not come up after
> Ethernet cable connect. The vendor's (Microchip, former Micrel) errata
> sheet 8688A.pdf describes the problem and possible workarounds in
> detail,
On Fri, Nov 23, 2018 at 11:05:04AM -0700, Jason Gunthorpe wrote:
> Date: Fri, 23 Nov 2018 11:05:04 -0700
> From: Jason Gunthorpe
> To: Kenneth Lee
> CC: Leon Romanovsky , Kenneth Lee ,
> Tim Sell , linux-...@vger.kernel.org, Alexander
> Shishkin , Zaibo Xu
> , zhangfei@foxmail.com, linux..
Hi Ard,
I love your patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
[also build test ERROR on v4.20-rc3 next-20181123]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Now that we have at least one bool option, we can export all of the
supported bool options via optmask when dumping them.
v2: new patch
Signed-off-by: Nikolay Aleksandrov
---
net/bridge/br.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/bridge/br.c b/net/bridge/br.c
in
Use the new boolopt API to add an option which disables learning from
link-local packets. The default is kept as before and learning is
enabled. This is a simple map from a boolopt bit to a bridge private
flag that is tested before learning.
v2: pass NULL for extack via sysfs
Signed-off-by: Nikol
We have been adding many new bridge options, a big number of which are
boolean but still take up netlink attribute ids and waste space in the skb.
Recently we discussed learning from link-local packets[1] and decided
yet another new boolean option will be needed, thus introducing this API
to save s
Hi,
This set adds a new bridge option which can control learning from
link-local packets, by default learning is on to be consistent and avoid
breaking users expectations. If the new no_linklocal_learn option is
enabled then the bridge will stop learning from link-local packets.
In order to save s
SO_TIMESTAMP, SO_TIMESTAMPNS and SO_TIMESTAMPING options, the
way they are currently defined, are not y2038 safe.
Subsequent patches in the series add new y2038 safe versions
of these options which provide 64 bit timestamps on all
architectures uniformly.
Hence, rename existing options with OLD tag
SOCK_RCVTSTAMPNS is never set alone. SOCK_RCVTSTAMP
is always set along with SOCK_RCVTSTAMPNS. This leads to
checking for two flag states whenever we need to check for
SOCK_RCVTSTAMPS.
Also SOCK_RCVTSTAMPS was the only flag that needed to be
checked in order to verify if either of the two flags ar
struct __kernel_old_timeval is supposed to have the same
layout as struct timeval. But, it was inadvarently missed
that __kernel_suseconds has a different definition for
sparc64.
Provide an asm-specific override that fixes it.
Reported-by: Arnd Bergmann
Suggested-by: Arnd Bergmann
Signed-off-by:
As part of y2038 solution, all internal uses of
struct timeval are replaced by struct __kernel_old_timeval
and struct compat_timeval by struct old_timeval32.
Make socket timestamps use these new types.
This is mainly to be able to verify that the kernel build
is y2038 safe when such non y2038 safe
The new type is meant to be used as a y2038 safe structure
to be used as part of cmsg data.
Presently the SO_TIMESTAMP socket option uses struct timeval
for timestamps. This is not y2038 safe.
Subsequent patches in the series add new y2038 safe socket
option to be used in the place of SO_TIMESTAMP_
Many architectures maintain an arch specific copy of the
file even though there are no differences with the asm-generic
one. Allow these architectures to use the generic one instead.
Signed-off-by: Deepa Dinamani
Cc: ch...@zankel.net
Cc: fenghua...@intel.com
Cc: t...@linutronix.de
Cc: schwidef...
Add SO_TIMESTAMP_NEW and SO_TIMESTAMPNS_NEW variants of
socket timestamp options.
These are the y2038 safe versions of the SO_TIMESTAMP_OLD
and SO_TIMESTAMPNS_OLD for all architectures.
Note that the format of scm_timestamping.ts[0] is not changed
in this patch.
Signed-off-by: Deepa Dinamani
Cc:
Add SO_TIMESTAMPING_NEW variant of socket timestamp options.
This is the y2038 safe versions of the SO_TIMESTAMPING_OLD
for all architectures.
Signed-off-by: Deepa Dinamani
Cc: ch...@zankel.net
Cc: fenghua...@intel.com
Cc: r...@twiddle.net
Cc: t...@linutronix.de
Cc: ubr...@linux.ibm.com
Cc: linux
The series introduces new socket timestamps that are
y2038 safe.
The time data types used for the existing socket timestamp
options: SO_TIMESTAMP, SO_TIMESTAMPNS and SO_TIMESTAMPING
are not y2038 safe. The series introduces SO_TIMESTAMP_NEW,
SO_TIMESTAMPNS_NEW and SO_TIMESTAMPING_NEW to replace th
From: Sudarsana Reddy Kalluru
Date: Thu, 22 Nov 2018 22:44:49 -0800
> - edev->flags |= QEDE_FLAG_IS_VF;
> + set_bit(QEDE_FLAGS_IS_VF, &edev->flags);
...
> - edev->flags |= QEDE_TX_TIMESTAMPING_EN;
> + set_bit(QEDE_FLAGS_TX_TIMESTAMPING_EN, &edev->fl
From: YueHaibing
Date: Fri, 23 Nov 2018 09:54:55 +0800
> Fix smatch warning:
>
> drivers/ptp/ptp_clock.c:298 ptp_clock_register() warn:
> passing zero to 'ERR_PTR'
>
> 'err' should be set while device_create_with_groups and
> pps_register_source fails
>
> Fixes: 85a66e550195 ("ptp: create "pi
From: Petr Machata
Date: Thu, 22 Nov 2018 23:27:52 +
> An offloading driver may need to have access to switchdev events on
> ports that aren't directly under its control. An example is a VXLAN port
> attached to a bridge offloaded by a driver. The driver needs to know
> about VLANs configured
From: Heiner Kallweit
Date: Thu, 22 Nov 2018 21:54:36 +0100
> This series includes a few functional improvements.
Series applied.
From: Salil Mehta
Date: Thu, 22 Nov 2018 14:09:40 +
> This patchset adds support of debugfs to the HNS3 driver.
>
> Support has been added to query info related to below items:
> 1. Queue related ("echo queue info [queue no] > cmd")
> 2. Flow Director ("echo dump fd tcam > cmd")
> 3. TC con
From: YueHaibing
Date: Thu, 22 Nov 2018 21:27:19 +0800
> ptp_clock_register never return NULL, so no need check this
> in cavium_ptp_probe.
>
> Signed-off-by: YueHaibing
Applied.
From: Quentin Schulz
Date: Thu, 22 Nov 2018 14:24:32 +0100
> A more featureful support for VSC8574 was recently added to the
> Microsemi (mscc.c) driver. I checked that features supported in the
> Vitesse driver are also supported in the Microsemi driver.
>
> Signed-off-by: Quentin Schulz
Appl
From: Yangtao Li
Date: Thu, 22 Nov 2018 07:34:41 -0500
> of_find_node_by_path() acquires a reference to the node
> returned by it and that reference needs to be dropped by its caller.
> This place doesn't do that, so fix it.
>
> Signed-off-by: Yangtao Li
Applied.
From: Linu Cherian
Date: Thu, 22 Nov 2018 17:18:33 +0530
> From: Linu Cherian
>
> Patch 1: Code cleanup
> Patch 2: Adds support for an unhandled hardware configuration
> Patch 3: Preparatory patch for enabling cgx lmac links
> Patch 4: Support for enabling cgx lmac links
Series applied.
From: Colin King
Date: Thu, 22 Nov 2018 10:05:01 +
> From: Colin Ian King
>
> Pointer hwdev is being dereferenced when declaring hwif , however, later
> on hwdev is being null checked, hence we have dereference before null
> check error. Fix this by assigning hwif and pdef only once hwdev h
From: Ursula Braun
Date: Thu, 22 Nov 2018 10:26:33 +0100
> here are more patches for SMC:
> * patches 1-3 and 7 are cleanups without functional change
> * patches 4-6 and 8 are optimizations of existing code
> * patches 9 and 10 introduce and exploit LLC message DELETE RKEY
Series applied.
From: Hangbin Liu
Date: Thu, 22 Nov 2018 16:15:28 +0800
> team_notify_peers() will send ARP and NA to notify peers. team_mcast_rejoin()
> will send multicast join group message to notify peers. We should do this when
> enabling/changed to a new port. But it doesn't make sense to do it when a port
Hi Cody,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on mac80211-next/master]
url:
https://github.com/0day-ci/linux/commits/Cody-Schuffelen/mac80211-next-rtnetlink-wifi-simulation-device/20181124-020949
base: https://git.kernel.org/pub/scm/linux/kernel/git/jbe
From: YueHaibing
Date: Thu, 22 Nov 2018 14:42:00 +0800
> fixes the smatch warning:
>
> drivers/net/ethernet/marvell/mvneta.c:4252 mvneta_ethtool_set_eee() warn:
> unsigned 'eee->tx_lpi_timer' is never less than zero.
>
> Signed-off-by: YueHaibing
Applied.
Document API and ABI for libbpf: naming convention, symbol visibility,
ABI versioning.
This is just a starting point. Documentation can be significantly
extended in the future to cover more topics.
ABI versioning section touches only a few basic points with a link to
more comprehensive documentat
More and more projects use libbpf and one day it'll likely be packaged
and distributed as DSO and that requires ABI versioning so that both
compatible and incompatible changes to ABI can be introduced in a safe
way in the future without breaking executables dynamically linked with a
previous versio
Since ABI versioning info is kept separately from the code it's easy to
forget to update it while adding a new API.
Add simple verification that all global symbols exported with LIBBPF_API
are versioned in libbpf.map version script.
The idea is to check that number of global symbols in libbpf-in.
This patch set adds ABI versioning and documentation to libbpf.
Patch 1 renames btf_get_from_id to btf__get_from_id to follow naming
convention.
Patch 2 adds version script and has more details on ABI versioning.
Patch 3 adds simple check that all global symbols are versioned.
Patch 4 documents a
From: Martin KaFai Lau
s/btf_get_from_id/btf__get_from_id/ to restore the API naming convention.
Signed-off-by: Martin KaFai Lau
Signed-off-by: Andrey Ignatov
---
tools/bpf/bpftool/map.c| 4 ++--
tools/bpf/bpftool/prog.c | 2 +-
tools/lib/bpf/btf.c
Daniel Borkmann [Thu, 2018-11-22 02:28 -0800]:
> On 11/21/2018 11:22 PM, Alexei Starovoitov wrote:
> > On 11/21/18 12:18 PM, Yonghong Song wrote:
> >> On 11/21/18 9:40 AM, Andrey Ignatov wrote:
> >>> More and more projects use libbpf and one day it'll likely be packaged
> >>> and distributed as DS
Make the formatting for map_type_name array consistent.
Signed-off-by: David Calavera
---
tools/bpf/bpftool/map.c | 46 -
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/tools/bpf/bpftool/map.c b/tools/bpf/bpftool/map.c
index b0ebbed7d1a6..c
Building tags produces warning:
ctags: Warning: kernel/bpf/local_storage.c:10: null expansion of name pattern
"\1"
Let's use the same fix as in commit <25528213fe9f75f4>, even though it
violates the usual code style.
Signed-off-by: Rustam Kovhaev
---
kernel/bpf/local_storage.c | 3 +--
1 file
On Fri, 23 Nov 2018 15:24:16 +0530 Anshuman Khandual
wrote:
> At present there are multiple places where invalid node number is encoded
> as -1. Even though implicitly understood it is always better to have macros
> in there. Replace these open encodings for an invalid node number with the
> glo
From: Andreas Fiedler
The TX stats should be started with the tx_stats_syncp,
there seems to be a copy/paste error in the driver.
Signed-off-by: Andreas Fiedler
Signed-off-by: Linus Walleij
---
drivers/net/ethernet/cortina/gemini.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
On Fri, Nov 23, 2018 at 2:09 PM David Miller wrote:
>
> From: Willem de Bruijn
> Date: Tue, 20 Nov 2018 13:00:18 -0500
>
> > From: Willem de Bruijn
> >
> > tpacket_snd sends packets with user pages linked into skb frags. It
> > notifies that pages can be reused when the skb is released by settin
On 11/22/2018 03:09 PM, Lorenz Bauer wrote:
> Add a new function, which encourages safe usage of the test interface.
> bpf_prog_test_run continues to work as before, but should be considered
> unsafe.
>
> Signed-off-by: Lorenz Bauer
Set looks good to me, thanks! Three small things below:
> ---
On arm64, modules are allocated from a 128 MB window which is close to
the core kernel, so that relative direct branches are guaranteed to be
in range (except in some KASLR configurations). Also, module_alloc()
is in charge of allocating KASAN shadow memory when running with KASAN
enabled.
This me
By default, BPF uses module_alloc() to allocate executable memory,
but this is not necessary on all arches and potentially undesirable
on some of them.
So break out the module_alloc() and module_memfree() calls into __weak
functions to allow them to be overridden in arch code.
Signed-off-by: Ard
The arm64 module region is a 128 MB region that is kept close to
the core kernel, in order to ensure that relative branches are
always in range. So using the same region for programs that do
not have this restriction is wasteful, and preferably avoided.
Now that the core BPF JIT code permits the a
On 11/23/2018 09:58 PM, Nikita V. Shirokov wrote:
> currently by default libbpf's bpf_object__open requires
> bpf's program to specify version in a code because of two things:
> 1) default prog type is set to KPROBE
> 2) KPROBE requires (in kernel/bpf/syscall.c) version to be specified
>
> in thi
On 11/22/2018 11:14 PM, Daniel T. Lee wrote:
> Currently, kprobe_events failure won't be handled properly.
> Due to calling system() indirectly to write to kprobe_events,
> it can't be identified whether an error is derived from kprobe or system.
>
> // buf = "echo '%c:%s %s' >> /s/k/d/t/kprob
On 11/23/2018 06:48 PM, David Calavera wrote:
> Hi,
>
> Sorry for the mistake, I'll send a new patch. Before doing that, I've
> noticed that the array of map names in tools/bpf/bpftool/map.c is very
> inconsistent in formatting, some lines use tabs to align the names, others
> use spaces, and othe
On Fri, 23 Nov 2018 at 22:07, Daniel Borkmann wrote:
>
> On 11/23/2018 10:41 AM, Ard Biesheuvel wrote:
> > By default, BPF uses module_alloc() to allocate executable memory,
> > but this is not necessary on all arches and potentially undesirable
> > on some of them.
> >
> > So break out the module
On 11/23/2018 10:41 AM, Ard Biesheuvel wrote:
> By default, BPF uses module_alloc() to allocate executable memory,
> but this is not necessary on all arches and potentially undesirable
> on some of them.
>
> So break out the module_alloc() and module_memfree() calls into __weak
> functions to allo
currently by default libbpf's bpf_object__open requires
bpf's program to specify version in a code because of two things:
1) default prog type is set to KPROBE
2) KPROBE requires (in kernel/bpf/syscall.c) version to be specified
in this patch i'm changing default prog type to UNSPEC and also chan
On 11/23/2018 05:43 PM, Martynas Pumputis wrote:
> A format string consisting of "%p" or "%s" followed by an invalid
> specifier (e.g. "%p%\n" or "%s%") could pass the check which
> would make format_decode (lib/vsprintf.c) to warn.
>
> Reported-by: syzbot+1ec5c5ec949c4adaa...@syzkaller.appspotmai
Martin Lau [Fri, 2018-11-23 10:44 -0800]:
> On Wed, Nov 21, 2018 at 02:22:14PM -0800, Alexei Starovoitov wrote:
> > On 11/21/18 12:18 PM, Yonghong Song wrote:
> > >
> > >
> > > On 11/21/18 9:40 AM, Andrey Ignatov wrote:
> > >> More and more projects use libbpf and one day it'll likely be package
On 11/23/2018 07:34 PM, Ben Hutchings wrote:
> User-space does not have access to the patched eBPF code, but we
> need to be able to test that patches are being applied. Therefore
> log distinct messages for each case that requires patching.
Thanks for the patches, Ben! Above is actually not the
From: Jason Wang
Date: Thu, 22 Nov 2018 14:36:31 +0800
> We don't support partial csumed packet since its metadata will be lost
> or incorrect during XDP processing. So fail the XDP set if guest_csum
> feature is negotiated.
>
> Fixes: f600b6905015 ("virtio_net: Add XDP support")
> Reported-by:
From: Jason Wang
Date: Thu, 22 Nov 2018 14:36:30 +0800
> We don't disable VIRTIO_NET_F_GUEST_CSUM if XDP was set. This means we
> can receive partial csumed packets with metadata kept in the
> vnet_hdr. This may have several side effects:
>
> - It could be overridden by header adjustment, thus i
From: Jeff Kirsher
Date: Wed, 21 Nov 2018 11:54:17 -0800
> This series contains updates to all of the Intel LAN drivers and
> documentation.
>
> Shannon Nelson updates the ixgbe kernel documentation to include IPsec
> hardware offload.
>
> Joe Perches cleans up whitespace issues in the igb driv
From: Eric Dumazet
Date: Wed, 21 Nov 2018 11:39:28 -0800
> We very often have few flows/chains to look at, and we
> might increase GRO_HASH_BUCKETS to 32 or 64 in the future.
>
> Signed-off-by: Eric Dumazet
Applied.
On Fri, Nov 23, 2018 at 11:25 AM David Miller wrote:
> My impression is that patch #2 needs some fixes in order to not
> lose dupacks. So there will be a respin of this.
>
> Thanks.
You are absolutely right, we will submit a v2 next week after TG holidays.
Thanks.
From: Eric Dumazet
Date: Wed, 21 Nov 2018 09:52:37 -0800
> While working on the SACK compression issue Jean-Louis Dupond
> reported, we found that his linux box was suffering very hard
> from tail drops on the socket backlog queue, because the opposite
> TCP stack was ont implementing latest RFC
From: Davide Caratti
Date: Wed, 21 Nov 2018 18:23:53 +0100
> commit f2cbd4852820 ("net/sched: act_police: fix race condition on state
> variables") introduces a new spinlock, but forgets its initialization.
> Ensure that tcf_police_init() initializes 'tcfp_lock' every time a 'police'
> action is
From: Paolo Abeni
Date: Wed, 21 Nov 2018 18:21:35 +0100
> Eric noted that with UDP GRO and NAPI timeout, we could keep a single
> UDP packet inside the GRO hash forever, if the related NAPI instance
> calls napi_gro_complete() at an higher frequency than the NAPI timeout.
> Willem noted that even
From: Hangbin Liu
Date: Wed, 21 Nov 2018 21:52:33 +0800
> When we add a new IPv6 address, we should also join corresponding
> solicited-node
> multicast address, unless the interface has IFF_NOARP flag, as function
> addrconf_join_solict() did. But if we remove IFF_NOARP flag later, we do
> not
From: Madalin Bucur
Date: Wed, 21 Nov 2018 13:41:06 +0200
> Add control of the DPAA portal interrupt coalescing settings from
> ethtool.
>
> changes from v2: read ithresh from HW, set previous values on failure
> changes from v1: added range checking for the QMan APIs
Series applied.
From: Magnus Damm
Date: Wed, 21 Nov 2018 20:21:08 +0900
> ravb: Duplex handling update V3
>
> [PATCH v3 01/02] ravb: Do not announce HDX as supported
> [PATCH v3 02/02] ravb: Clean up duplex handling
Series applied to net-next.
From: Ganesh Goudar
Date: Wed, 21 Nov 2018 13:40:24 +0530
> From: Santosh Rastapur
>
> If the fw supports returning VIN/VIVLD in FW_VI_CMD save it
> in port_info structure else retrieve these from viid and save
> them in port_info structure. Do the same for smt_idx from
> FW_VI_MAC_CMD
>
> Si
From: Doug Berger
Date: Tue, 20 Nov 2018 15:17:01 -0800
> Commit c5a54bbcecec ("net: bcmgenet: abort suspend on error")
> mistakenly introduced register accesses that should not occur
> in bcmgenet_wol_power_up_cfg().
>
> Fixes: c5a54bbcecec ("net: bcmgenet: abort suspend on error")
> Signed-off
From: Willem de Bruijn
Date: Tue, 20 Nov 2018 13:00:18 -0500
> From: Willem de Bruijn
>
> tpacket_snd sends packets with user pages linked into skb frags. It
> notifies that pages can be reused when the skb is released by setting
> skb->destructor to tpacket_destruct_skb.
>
> This can cause da
From: Felix Jia
Date: Tue, 20 Nov 2018 14:53:24 +1300
> +struct ip6_tnl_rule {
> + u8 version;
> + struct in6_addr ipv6_subnet;
> + u8 ipv6_prefixlen;
> + struct in_addr ipv4_subnet;
> + u8 ipv4_prefixlen;
> + u8 ea_length;
> + u8 psid_offset;
Please arrange the membe
On Wed, Nov 21, 2018 at 02:22:14PM -0800, Alexei Starovoitov wrote:
> On 11/21/18 12:18 PM, Yonghong Song wrote:
> >
> >
> > On 11/21/18 9:40 AM, Andrey Ignatov wrote:
> >> More and more projects use libbpf and one day it'll likely be packaged
> >> and distributed as DSO and that requires ABI ver
After switching the r8169 driver to use phylib some user reported that
their network is broken. This was caused by the genphy PHY driver being
used instead of the dedicated PHY driver for the RTL8211B. Users
reported that loading the Realtek PHY driver module upfront fixes the
issue. See also this
This is needed to test that code is being patched when it should be.
Signed-off-by: Ben Hutchings
---
tools/testing/selftests/bpf/test_verifier.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/test_verifier.c
b/tools/testing/selftests
Test that the defence added by commit af86ca4e3088 "bpf: Prevent
memory disambiguation attack" is actually being applied.
Signed-off-by: Ben Hutchings
---
tools/testing/selftests/bpf/test_verifier.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/tools/testing/selftests/bpf/
User-space does not have access to the patched eBPF code, but we
need to be able to test that patches are being applied. Therefore
log distinct messages for each case that requires patching.
Signed-off-by: Ben Hutchings
---
kernel/bpf/verifier.c | 13 +
1 file changed, 13 insertions
This series adds log messages for all patching done by the verifier,
and a test case to verify that the patch to defend against SSB
exploitation is applied where needed.
Ben.
Ben Hutchings (3):
bpf/verifier: Log instruction patching when verbose logging is enabled
selftests/bpf: Add the abili
On Fri, Nov 23, 2018 at 04:02:42PM +0800, Kenneth Lee wrote:
> It is already part of Jean's patchset. And that's why I built my solution on
> VFIO in the first place. But I think the concept of SVA and PASID is not
> compatible with the original VFIO concept space. You would not share your
> whol
On Fri, Nov 23, 2018 at 07:01:51PM +0100, Quentin Schulz wrote:
> The vsc85xx_default_config function called in the vsc85xx_config_init
> function which is used by VSC8530, VSC8531, VSC8540 and VSC8541 PHYs
> mistakenly calls phy_read and phy_write in-between phy_select_page and
> phy_restore_page.
On Fri, Nov 23, 2018 at 03:46:50PM -0200, Fabio Estevam wrote:
> The correct form is "can be probed", so fix the typo.
>
> Signed-off-by: Fabio Estevam
Reviewed-by: Andrew Lunn
Andrew
The vsc85xx_default_config function called in the vsc85xx_config_init
function which is used by VSC8530, VSC8531, VSC8540 and VSC8541 PHYs
mistakenly calls phy_read and phy_write in-between phy_select_page and
phy_restore_page.
phy_select_page and phy_restore_page actually take and release the MDI
Hi Andrew,
On Fri, Nov 23, 2018 at 04:08:06PM +0100, Andrew Lunn wrote:
> On Fri, Nov 23, 2018 at 09:16:36AM +0100, Quentin Schulz wrote:
> > The vsc85xx_default_config function called in the vsc85xx_config_init
> > function which is used by VSC8530, VSC8531, VSC8540 and VSC8541 PHYs
> > mistakenl
The correct form is "can be probed", so fix the typo.
Signed-off-by: Fabio Estevam
---
Documentation/devicetree/bindings/net/dsa/dsa.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/dsa/dsa.txt
b/Documentation/devicetree/bindings/net/
Reset snd_queue tso_hdrs pointer to NULL in nicvf_free_snd_queue routine
since it is used to check if tso dma descriptor queue has been previously
allocated. The issue can be triggered with the following reproducer:
$ip link set dev enP2p1s0v0 xdpdrv obj xdp_dummy.o
$ip link set dev enP2p1s0v0 xdp
Could be a bug, or just how it works?
Begin forwarded message:
Date: Thu, 22 Nov 2018 22:51:12 +
From: bugzilla-dae...@bugzilla.kernel.org
To: step...@networkplumber.org
Subject: [Bug 201773] New: IP_FREEBIND doesn’t counteract global
https://bugzilla.kernel.org/show_bug.cgi?id=201773
Send frames back on the same port for XDP_TX action.
Since the frame buffers have been allocated by us, we can recycle
them directly into the Rx buffer pool instead of requesting a
confirmation frame upon transmission complete.
Signed-off-by: Ioana Radulescu
---
drivers/net/ethernet/freescale/dp
Add support for XDP programs. Only XDP_PASS, XDP_DROP and XDP_TX
actions are supported for now. Frame header changes are also
allowed.
Ioana Radulescu (8):
dpaa2-eth: Add basic XDP support
dpaa2-eth: Allow XDP header adjustments
dpaa2-eth: Move function
dpaa2-eth: Release buffers back to p
We keep one XDP program reference per channel. The only actions
supported for now are XDP_DROP and XDP_PASS.
Until now we didn't enforce a maximum size for Rx frames based
on MTU value. Change that, since for XDP mode we must ensure no
scatter-gather frames can be received.
Signed-off-by: Ioana R
Remove one unused counter. Move the Tx portal busy counter to
the channel stats, since it logically belongs here.
Reorder fields in channel stats structure to match the ethtool
strings order and make it easier to print them with ethtool -S.
Signed-off-by: Ioana Radulescu
---
drivers/net/etherne
1 - 100 of 158 matches
Mail list logo
