[linux-yocto] [PATCH] x86_64: expand kernel stack to 16K

From: Minchan Kim minc...@kernel.org commit 6538b8ea886e472f4431db8ca1d60478f838d14b upstream While I play inhouse patches with much memory pressure on qemu-kvm, 3.14 kernel was randomly crashed. The reason was kernel stack overflow. When I investigated the problem, the callstack was a little

[linux-yocto] [PATCH] [RFC] cgroups: Resource controller for open files

From: He Zhe zhe...@windriver.com Add a resource controller for limiting the number of open file handles. This allows us to catch misbehaving processes and return EMFILE instead of ENOMEM for kernel memory limits. Signed-off-by: Binder Makin meri...@google.com Port from lkml:

[linux-yocto] [PATCH] cgroups: enable file handles resource controller

From: He Zhe zhe...@windriver.com Enable file handles resource controller for convenience Signed-off-by: He Zhe zhe...@windriver.com --- meta/cfg/kernel-cache/features/cgroups/cgroups.cfg |1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/features/cgroups/cgroups.cfg

[linux-yocto] [PATCH 1/2] [RFC]cgroups: Resource controller for open files.

From: Binder Makin meri...@google.com lkml https://lkml.org/lkml/2014/7/2/640 upstream Add a resource controller for limiting the number of open file handles. This allows us to catch misbehaving processes and return EMFILE instead of ENOMEM for kernel memory limits. Signed-off-by: Binder Makin

[linux-yocto] [PATCH 2/2] Fix [RFC] cgroups: Resource controller for open files.

From: He Zhe zhe...@windriver.com The original patch is based on: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git fad01e866afdbe01a1f3ec06a39c3a8b9e197014 3.15-rc8 Modify variable and macro in fs/filescontrol.c and include/linux/cgroup_subsys.h according to target version.

[linux-yocto] [PATCH 1/2] [RFC]cgroups: Resource controller for open files.

From: Binder Makin meri...@google.com Add a resource controller for limiting the number of open file handles. This allows us to catch misbehaving processes and return EMFILE instead of ENOMEM for kernel memory limits. Signed-off-by: Binder Makin meri...@google.com --- fs/Makefile

[linux-yocto] [PATCH 2/2] Fix [RFC] cgroups: Resource controller for open files.

From: He Zhe zhe...@windriver.com The original patch is based on: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git fad01e866afdbe01a1f3ec06a39c3a8b9e197014 3.15-rc8 Modify variable and macro in fs/filescontrol.c and include/linux/cgroup_subsys.h according to target version.

[linux-yocto] [PATCH 06/29] openvswitch: flow_netlink: Use pr_fmt to OVS_NLERR output

From: Joe Perches j...@perches.com commit 2235ad1c3ac545bd8fc2c026be5be16d98b9a891 upstream Add openvswitch: prefix to OVS_NLERR output to match the other OVS_NLERR output of datapath.c Signed-off-by: Joe Perches j...@perches.com Signed-off-by: Jesse Gross je...@nicira.com Signed-off-by: He

[linux-yocto] [PATCH 01/29] openvswitch: use const in some local vars and casts

From: Daniele Di Proietto daniele.di.proie...@gmail.com commit 7085130bab2f9c5b8d61bff73b01dc8195d0f974 upstream In few functions, const formal parameters are assigned or cast to non-const. These changes suppress warnings if compiled with -Wcast-qual. Signed-off-by: Daniele Di Proietto

[linux-yocto] [PATCH 02/29] openvswitch: avoid warnings in vport_from_priv

From: Daniele Di Proietto daniele.di.proie...@gmail.com commit d0b4da137508db3d38998eae7f62c0f9699ee08c upstream This change, firstly, avoids declaring the formal parameter const, since it is treated as non const. (to avoid -Wcast-qual) Secondly, it cast the pointer from void* to u8*, since it

[linux-yocto] [PATCH 04/29] openvswitch: Added (unsigned long long) cast in printf

From: Daniele Di Proietto daniele.di.proie...@gmail.com commit cc23ebf3bb4348fb022c0d25494307459bb2e539 upstream This is necessary, since u64 is not unsigned long long in all architectures: u64 could be also uint64_t. Signed-off-by: Daniele Di Proietto daniele.di.proie...@gmail.com

[linux-yocto] [PATCH 03/29] openvswitch: avoid cast-qual warning in vport_priv

From: Daniele Di Proietto daniele.di.proie...@gmail.com commit 07dc0602c5976cfc36ccffe5c6d73234f204d585 upstream This function must cast a const value to a non const value. By adding an uintptr_t cast the warning is suppressed. To avoid the cast (proper solution) several function signatures must

[linux-yocto] [PATCH 07/29] openvswitch: Use ether_addr_copy

From: Joe Perches j...@perches.com commit 8c63ff09bddf944ab0033fea97aacfadfffa76de upstream It's slightly smaller/faster for some architectures. Signed-off-by: Joe Perches j...@perches.com Signed-off-by: Jesse Gross je...@nicira.com Signed-off-by: He Zhe zhe...@windriver.com ---

[linux-yocto] [PATCH 05/29] openvswitch: Use net_ratelimit in OVS_NLERR

From: Joe Perches j...@perches.com commit 1815a8831fb04c60d73627816cb0b596266e9bee upstream Each use of pr_level_once has a per-site flag. Some of the OVS_NLERR messages look as if seeing them multiple times could be useful, so use net_ratelimit() instead of pr_info_once. Signed-off-by: Joe

[linux-yocto] [PATCH 08/29] openvswitch: Remove 5-tuple optimization.

From: Jarno Rajahalme jrajaha...@nicira.com commit 23dabf88abb48a866fdb19ee08ebcf1ddd9b1840 upstream The 5-tuple optimization becomes unnecessary with a later per-NUMA node stats patch. Remove it first to make the changes easier to grasp. Signed-off-by: Jarno Rajahalme jrajaha...@nicira.com

[linux-yocto] [PATCH 09/29] openvswitch: Per NUMA node flow stats.

From: Jarno Rajahalme jrajaha...@nicira.com commit 63e7959c4b9bd6f791061c460a22d9ee32ae2240 upstream Keep kernel flow stats for each NUMA node rather than each (logical) CPU. This avoids using the per-CPU allocator and removes most of the kernel-side OVS locking overhead otherwise on the top of

[linux-yocto] [PATCH 11/29] openvswitch: Use TCP flags in the flow key for stats.

From: Jarno Rajahalme jrajaha...@nicira.com commit 88d73f6c411ac2f057829b93b3cf202ee551f6cb upstream We already extract the TCP flags for the key, might as well use that for stats. Signed-off-by: Jarno Rajahalme jrajaha...@nicira.com Acked-by: Pravin B Shelar pshe...@nicira.com Signed-off-by:

[linux-yocto] [PATCH 12/29] net/openvswitch: Use with RCU_INIT_POINTER(x, NULL) in vport-gre.c

From: Monam Agarwal monamagarwal...@gmail.com commit 944df8ae84d88f5e8eb027990dad2cfa4fbe4be5 upstream This patch replaces rcu_assign_pointer(x, NULL) with RCU_INIT_POINTER(x, NULL) The rcu_assign_pointer() ensures that the initialization of a structure is carried out before storing a pointer

[linux-yocto] [PATCH 18/29] openvswitch: Minimize dp and vport critical sections.

From: Jarno Rajahalme jrajaha...@nicira.com commit 6093ae9abac18871afd0bbc5cf093dff53112fcb upstream Move most memory allocations away from the ovs_mutex critical sections. vport allocations still happen while the lock is taken, as changing that would require major refactoring. Also, vports are

[linux-yocto] [PATCH 16/29] openvswitch: Build flow cmd netlink reply only if needed.

From: Jarno Rajahalme jrajaha...@nicira.com commit fb5d1e9e127ad1542e5db20cd8620a1509baef69 upstream Use netlink_has_listeners() and NLM_F_ECHO flag to determine if a reply is needed or not for OVS_FLOW_CMD_NEW, OVS_FLOW_CMD_SET, or OVS_FLOW_CMD_DEL. Currently, OVS userspace does not request a

[linux-yocto] [PATCH 17/29] openvswitch: Make flow mask removal symmetric.

From: Jarno Rajahalme jrajaha...@nicira.com commit 56c19868e115fcf8d62d843e1b9616bb9837d0db upstream Masks are inserted when flows are inserted to the table, so it is logical to correspondingly remove masks when flows are removed from the table, in ovs_flow_table_remove(). This allows

[linux-yocto] [PATCH 15/29] openvswitch: Clarify locking.

From: Jarno Rajahalme jrajaha...@nicira.com commit bb6f9a708d4067713afae2e9eb2637f6b4c01ecb upstream Remove unnecessary locking from functions that are always called with appropriate locking. Signed-off-by: Jarno Rajahalme jrajaha...@nicira.com Signed-off-by: Thomas Graf tg...@redhat.com

[linux-yocto] [PATCH 14/29] openvswitch: Avoid assigning a NULL pointer to flow actions.

From: Jarno Rajahalme jrajaha...@nicira.com commit be52c9e96a6657d117bb0ec6e11438fb246af5c7 upstream Flow SET can accept an empty set of actions, with the intended semantics of leaving existing actions unmodified. This seems to have been brokin after OVS 1.7, as we have assigned the flow's

[linux-yocto] [PATCH 13/29] openvswitch: Compact sw_flow_key.

From: Jarno Rajahalme jrajaha...@nicira.com commit 1139e241ec436b9e9610c7a33ac5c6657f87fda1 upstream Minimize padding in sw_flow_key and move 'tp' top the main struct. These changes simplify code when accessing the transport port numbers and the tcp flags, and makes the sw_flow_key 8 bytes

[linux-yocto] [PATCH 19/29] openvswitch: Fix typo.

From: Jarno Rajahalme jrajaha...@nicira.com commit eb07265904d6ee95497aba0f3cbd2ae6d9c39a97 upstream Incorrect struct name was confusing, even though otherwise inconsequental. Signed-off-by: Jarno Rajahalme jrajaha...@nicira.com Signed-off-by: Pravin B Shelar pshe...@nicira.com Signed-off-by:

[linux-yocto] [PATCH 28/29] openvswitch: Fix tracking of flags seen in TCP flows.

From: Ben Pfaff b...@nicira.com commit ad55200734c65a3ec5d0c39d6ea904008baea536 upstream Flow statistics need to take into account the TCP flags from the packet currently being processed (in 'key'), not the TCP flags matched by the flow found in the kernel flow table (in 'flow'). This bug made

[linux-yocto] [PATCH 21/29] openvswitch: Reduce locking requirements.

From: Jarno Rajahalme jrajaha...@nicira.com commit 0e9796b4af9ef490e203158cb738a5a4986eb75c upstream Reduce and clarify locking requirements for ovs_flow_cmd_alloc_info(), ovs_flow_cmd_fill_info() and ovs_flow_cmd_build_info(). A datapath pointer is available only when holding a lock. Change

[linux-yocto] [PATCH 23/29] openvswitch: Split ovs_flow_cmd_new_or_set().

From: Jarno Rajahalme jrajaha...@nicira.com commit 37bdc87ba00dadd0156db77ba48224d042202435 upstream Following patch will be easier to reason about with separate ovs_flow_cmd_new() and ovs_flow_cmd_set() functions. Signed-off-by: Jarno Rajahalme jrajaha...@nicira.com Signed-off-by: Pravin B

[linux-yocto] [PATCH 26/29] openvswitch: Fix a double free bug for the sample action

From: Andy Zhou az...@nicira.com commit fe984c08e20f0fc2b4666bf8eeeb02605568387b upstream When sample action returns with an error, the skb has already been freed. This patch fix a bug to make sure we don't free it again. This bug introduced by commit ccb1352e76cff05 (net: Add Open vSwitch

[linux-yocto] [PATCH 25/29] openvswitch: Simplify genetlink code.

From: Pravin B Shelar pshe...@nicira.com commit 0c200ef94c9492205e18a18c25650cf27939889c upstream Following patch get rid of struct genl_family_and_ops which is redundant due to changes to struct genl_family. Signed-off-by: Kyle Mestery mest...@noironetworks.com Acked-by: Kyle Mestery

[linux-yocto] [PATCH 24/29] openvswitch: Minimize ovs_flow_cmd_new|set critical sections.

From: Jarno Rajahalme jrajaha...@nicira.com commit 893f139b9a6c00c097b9082a90f3041cfb3a0d20 upstream Signed-off-by: Jarno Rajahalme jrajaha...@nicira.com Signed-off-by: Pravin B Shelar pshe...@nicira.com Signed-off-by: He Zhe zhe...@windriver.com --- net/openvswitch/datapath.c | 192

[linux-yocto] [PATCH 20/29] openvswitch: Fix ovs_flow_stats_get/clear RCU dereference.

From: Jarno Rajahalme jrajaha...@nicira.com commit 86ec8dbae27e5fa2b5d54f10f77286d9ef55732a upstream For ovs_flow_stats_get() using ovsl_dereference() was wrong, since flow dumps call this with RCU read lock. ovs_flow_stats_clear() is always called with ovs_mutex, so can use ovsl_dereference().

[linux-yocto] [PATCH 22/29] openvswitch: Minimize ovs_flow_cmd_del critical section.

From: Jarno Rajahalme jrajaha...@nicira.com commit aed067783e505bf66dcafa8647d08619eb5b1c55 upstream ovs_flow_cmd_del() now allocates reply (if needed) after the flow has already been removed from the flow table. If the reply allocation fails, a netlink error is signaled with netlink_set_err(),

[linux-yocto] [PATCH 27/29] openvswitch: supply a dummy err_handler of gre_cisco_protocol to prevent kernel crash

From: Wei Zhang asuka@163.com commit e0bb8c44ed5cfcc56b571758ed966ee48779024c upstream When use gre vport, openvswitch register a gre_cisco_protocol but does not supply a err_handler with it. The gre_cisco_err() in net/ipv4/gre_demux.c expect err_handler be provided with the

[linux-yocto] [PATCH 29/29] openvswitch: Use exact lookup for flow_get and flow_del.

From: Alex Wang al...@nicira.com commit 4a46b24e147dfa9b858026da02cad0bdd4e149d2 upstream Due to the race condition in userspace, there is chance that two overlapping megaflows could be installed in datapath. And this causes userspace unable to delete the less inclusive megaflow flow even after

[linux-yocto] [PATCH 01/10] vhost: don't open-code sockfd_put()

From: Al Viro v...@zeniv.linux.org.uk commit 09aaacf02a3e88870ed5cad038a5bc822c947904 upstream Signed-off-by: Al Viro v...@zeniv.linux.org.uk Signed-off-by: He Zhe zhe...@windriver.com --- drivers/vhost/net.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git

[linux-yocto] [PATCH 03/10] vhost/scsi: Add preallocation of protection SGLs

From: Nicholas Bellinger n...@linux-iscsi.org commit b1935f687bb93b207ef690f7debc0e9921fc484f upstream This patch updates tcm_vhost_make_nexus() to pre-allocate per descriptor tcm_vhost_cmd-tvc_prot_sgl[] used to expose protection SGLs from within virtio-scsi guest memory to vhost-scsi. Cc:

[linux-yocto] [PATCH 02/10] vhost/scsi: Move sanity check into vhost_scsi_map_iov_to_sgl

From: Nicholas Bellinger n...@linux-iscsi.org commit 5a01d08217e39f3d36d3ca160361c7b019ff1598 upstream Move the overflow check for sgl_count TCM_VHOST_PREALLOC_SGLS into vhost_scsi_map_iov_to_sgl() so that it's based on the total number of SGLs for all IOVs, instead of single IOVs. Also,

[linux-yocto] [PATCH 08/10] vhost: move acked_features to VQs

From: Michael S. Tsirkin m...@redhat.com commit ea16c51433510f7f758382dec5b933fc0797f244 upstream Refactor code to make sure features are only accessed under VQ mutex. This makes everything simpler, no need for RCU here anymore. Signed-off-by: Michael S. Tsirkin m...@redhat.com Signed-off-by:

[linux-yocto] [PATCH 05/10] vhost/scsi: Enable T10 PI IOV - SGL memory mapping

From: Nicholas Bellinger n...@linux-iscsi.org commit 95e7c4341b8e28dae5204378087c1e2a115abc82 upstream This patch updates vhost_scsi_handle_vq() to check for the existance of virtio_scsi_cmd_req_pi comparing vq-iov[0].iov_len in order to calculate seperate data + protection SGLs from data_num.

[linux-yocto] [PATCH 09/10] vhost: move memory pointer to VQs

From: Michael S. Tsirkin m...@redhat.com commit 47283bef7ed356629467d1fac61687756e48f254 upstream commit 2ae76693b8bcabf370b981cd00c36cd41d33fabc vhost: replace rcu with mutex replaced rcu sync for memory accesses with VQ mutex locl/unlock. This is correct since all accesses are under VQ

[linux-yocto] [PATCH 06/10] vhost-net: extend device allocation to vmalloc

From: Michael S. Tsirkin m...@redhat.com commit 23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 upstream Michael Mueller provided a patch to reduce the size of vhost-net structure as some allocations could fail under memory pressure/fragmentation. We are still left with high order allocations though.

[linux-yocto] [PATCH 07/10] vhost: replace rcu with mutex

From: Michael S. Tsirkin m...@redhat.com commit 98f9ca0a3faa99b7388578d55eccecf272be4038 upstream All memory accesses are done under some VQ mutex. So lock/unlock all VQs is a faster equivalent of synchronize_rcu() for memory access changes. Some guests cause a lot of these changes, so it's

[linux-yocto] [PATCH 04/10] vhost/scsi: Add T10 PI IOV - SGL memory mapping logic

From: Nicholas Bellinger n...@linux-iscsi.org commit e31885dd901e80d5bd528c1cbedde07ebbf051b2 upstream This patch adds vhost_scsi_map_iov_to_prot() to perform the mapping of T10 data integrity memory between virtio iov + struct scatterlist using get_user_pages_fast() following existing code. As

[linux-yocto] [PATCH 10/10] vhost-scsi: Include prot_bytes into expected data transfer length

From: Nicholas Bellinger n...@linux-iscsi.org commit 9f977ef7b671f6169eca78bf40f230fe84b7c7e5 upstream This patch updates vhost_scsi_get_tag() to accept the combined expected data transfer length + T10 PI bytes as the value passed into target_submit_cmd(). This is required now that target-core

[linux-yocto] [PATCH 5/26] net: filter: move filter accounting to filter core

From: Daniel Borkmann dbork...@redhat.com commit fbc907f0b1386c02e00516aa78a0fa6b0454fd0b upstream This patch basically does two things, i) removes the extern keyword from the include/linux/filter.h file to be more consistent with the rest of Joe's changes, and ii) moves filter accounting into

[linux-yocto] [PATCH 1/26] tools: bpf_dbg: various misc code cleanups

From: Daniel Borkmann dbork...@redhat.com commit 7debf7806e0e984ea7e43cc271dc9400b0dffc14 upstream Lets clean up bpf_dbg a bit and improve its code slightly in various areas: i) Get rid of some macros as there's no good reason for keeping them, ii) remove one unused variable and reduce scope of

[linux-yocto] [PATCH 4/26] net: filter: keep original BPF program around

From: Daniel Borkmann dbork...@redhat.com commit a3ea269b8bcdbb0c5fa2fd449a436e7987446975 upstream In order to open up the possibility to internally transform a BPF program into an alternative and possibly non-trivial reversible representation, we need to keep the original BPF program around, so

[linux-yocto] [PATCH 10/26] net: filter: seccomp: fix wrong decoding of BPF_S_ANC_SECCOMP_LD_W

From: Daniel Borkmann dbork...@redhat.com commit 8c482cdc358ef931ee02262e0a4ef0f29946aa0c upstream While reviewing seccomp code, we found that BPF_S_ANC_SECCOMP_LD_W has been wrongly decoded by commit a8fc927780 (sk-filter: Add ability to get socket filter program (v2)) into the opcode

[linux-yocto] [PATCH 9/26] filter: prevent nla extensions to peek beyond the end of the message

From: Mathias Krause mini...@googlemail.com commit 05ab8f2647e4221cbdb3856dd7d32bd5407316b3 upstream The BPF_S_ANC_NLATTR and BPF_S_ANC_NLATTR_NEST extensions fail to check for a minimal message length before testing the supplied offset to be within the bounds of the message. This allows the

[linux-yocto] [PATCH 12/26] net: filter: initialize A and X registers

From: Alexei Starovoitov a...@plumgrid.com commit 83d5b7ef99c9f05e87333b334a638de1264ab8e4 upstream exisiting BPF verifier allows uninitialized access to registers, 'ret A' is considered to be a valid filter. So initialize A and X to zero to prevent leaking kernel memory In the future BPF

[linux-yocto] [PATCH 11/26] filter: added BPF random opcode

From: Chema Gonzalez ch...@google.com commit 4cd3675ebf74d7f559038ded6aa8088e4099a83d upstream Added a new ancillary load (bpf call in eBPF parlance) that produces a 32-bit random number. We are implementing it as an ancillary load (instead of an ISA opcode) because (a) it is simpler, (b) allows

[linux-yocto] [PATCH 13/26] sched, cls: check if we could overwrite actions when changing a filter

From: Cong Wang cw...@twopensource.com commit 2f7ef2f8790f5bf53db4fc6b2310943139285827 upstream When actions are attached to a filter, they are a part of the filter itself, so when changing a filter we should allow to overwrite the actions inside as well. In my specific case, when I tried to

[linux-yocto] [PATCH 8/26] net: filter: be more defensive on div/mod by X==0

From: Daniel Borkmann dbork...@redhat.com commit 5f9fde5f799df7156eeb3fa58282e9fd2f38a5f8 upstream The old interpreter behaviour was that we returned with 0 whenever we found a division by 0 would take place. In the new interpreter we would currently just skip that instead and continue

[linux-yocto] [PATCH 14/26] bpf_dbg: fix wrong register usage

From: Brendan Hickey bhic...@google.com commit e5744fe9d262d11131916d04ea79ea539fe296c0 upstream The AND instruction is erroneously using the X register instead of the K register. Signed-off-by: Brendan Hickey bhic...@google.com Signed-off-by: Daniel Borkmann dbork...@redhat.com Signed-off-by:

[linux-yocto] [PATCH 7/26] net: filter: minor: fix kdoc in __sk_run_filter

From: Daniel Borkmann dbork...@redhat.com commit 01d32f6e5a3f709a90aadbb73723e77a96d67cb2 upstream This minor patch fixes the following warning when doing a `make htmldocs`: DOCPROC Documentation/DocBook/networking.xml Warning(.../net/core/filter.c:135): No description found for parameter

[linux-yocto] [PATCH 21/26] net: filter: Fix redefinition warnings on x86-64.

From: David S. Miller da...@davemloft.net commit 1268e253a81e504bc5d5cb7f887dbd538984f137 upstream Do not collide with the x86-64 PTRACE user API namespace. net/core/filter.c:57:0: warning: R8 redefined [enabled by default] arch/x86/include/uapi/asm/ptrace-abi.h:38:0: note: this is the location

[linux-yocto] [PATCH 17/26] net: filter: misc/various cleanups

From: Daniel Borkmann dbork...@redhat.com commit eb9672f4a14bb7058c44efcc31c89737a7724d2c upstream This contains only some minor misc cleanpus. We can spare us the extra variable declaration in __skb_get_pay_offset(), the cast in __get_random_u32() is rather unnecessary and in

[linux-yocto] [PATCH 26/26] net: e1000e calls skb_set_hash

From: Tom Herbert therb...@google.com commit e25909bcdf2e43caa4ea9b1283ade2749da35639 upstream Drivers should call skb_set_hash to set the hash and its type in an skbuff. Signed-off-by: Tom Herbert therb...@google.com Tested-by: Aaron Brown aaron.f.br...@intel.com Signed-off-by: Jeff Kirsher

[linux-yocto] [PATCH 23/26] net: filter: x86: internal BPF JIT

From: Alexei Starovoitov a...@plumgrid.com commit 622582786c9e041d0bd52bde201787adeab249f8 upstream Maps all internal BPF instructions into x86_64 instructions. This patch replaces original BPF x64 JIT with internal BPF x64 JIT. sysctl net.core.bpf_jit_enable is reused as on/off switch.

[linux-yocto] [PATCH 25/26] net: ppp: use sk_unattached_filter api

From: Daniel Borkmann dbork...@redhat.com commit 568f194e8bd16c353ad50f9ab95d98b20578a39d upstream For the ppp driver, there are currently two open-coded BPF filters in use, that is, pass_filter and active_filter. Migrate both to make proper use of sk_unattached_filter_{create,destroy} API so

[linux-yocto] [PATCH 1/1] Revert net: Rename skb-rxhash to skb-hash

From: He Zhe zhe...@windriver.com Revert unnecessary renaming for BPF. Build will fail if related drivers are enabled but do not get updated accordingly. Signed-off-by: He Zhe zhe...@windriver.com --- arch/arm/net/bpf_jit_32.c | 4 ++-- arch/powerpc/net/bpf_jit_comp.c | 4 ++--

[linux-yocto] [V2][PATCH 1/1] net: Rename skb-hash to skb-rxhash

From: He Zhe zhe...@windriver.com This is used to undo the previous commit net: Rename skb-rxhash to skb-hash which introduces unnecessary renamings for BPF. Build will fail if related drivers are enabled but do not get updated accordingly. Since the context has been changed by other commits in

[linux-yocto] [PATCH 1/1] qemuarm64: create bsp config

From: He Zhe zhe...@windriver.com This is the initial meta data for qemu arm64 bsp that supports qemu's virt for aarch64. Signed-off-by: He Zhe zhe...@windriver.com --- .../bsp/qemuarm64/qemuarm64-standard.scc | 9 +++ meta/cfg/kernel-cache/bsp/qemuarm64/qemuarm64.cfg | 29

[linux-yocto] [PATCH 1/1] yaffs2: Add patch to fix missing checkpoint

From: He Zhe Signed-off-by: He Zhe --- .../yaffs2-fix-missing-checkpoint-on-yaffs.patch | 85 ++ features/yaffs2/yaffs2.scc | 1 + 2 files changed, 86 insertions(+) create mode 100644

[linux-yocto] [PATCH 0/1] Add patch to fix missing checkpoint on yaffs2, for yocto-4.1

From: He Zhe Please apply this set of patches on yocto-4.1 branch from git://git.yoctoproject.org/yocto-kernel-cache He Zhe (1): yaffs2: Add patch to fix missing checkpoint .../yaffs2-fix-missing-checkpoint-on-yaffs.patch | 85 ++

[linux-yocto] [PATCH 0/1] Add patch to fix missing checkpoint on yaffs2, for master

From: He Zhe Please apply this set of patches on master branch from git://git.yoctoproject.org/yocto-kernel-cache He Zhe (1): yaffs2: Add patch to fix missing checkpoint .../yaffs2-fix-missing-checkpoint-on-yaffs.patch | 85 ++

[linux-yocto] [PATCH 1/1] yaffs2: Add patch to fix missing checkpoint

From: He Zhe Signed-off-by: He Zhe --- .../yaffs2-fix-missing-checkpoint-on-yaffs.patch | 85 ++ features/yaffs2/yaffs2.scc | 1 + 2 files changed, 86 insertions(+) create mode 100644

[linux-yocto] [kernel-cache][PATCH] cgl: Add cgl features

From: He Zhe Add features for Carrier Grade Linux https://wiki.linuxfoundation.org/cgl/start Signed-off-by: He Zhe --- cfg/dmm.cfg | 1 + cfg/dmm.scc | 4 cfg/drbd.cfg | 1 +

[linux-yocto] [PATCH] selinux: Fix audit.scc path

From: He Zhe Signed-off-by: He Zhe --- cgl/features/selinux/selinux.scc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cgl/features/selinux/selinux.scc b/cgl/features/selinux/selinux.scc index 6621e2a..04c8d93 100644 ---

[linux-yocto] [PATCH 1/2][v2] cgl: Add cgl features

From: He Zhe Add features for Carrier Grade Linux https://wiki.linuxfoundation.org/cgl/start Signed-off-by: He Zhe --- cgl/cfg/dmm.cfg | 1 + cgl/cfg/dmm.scc | 4 cgl/cfg/drbd.cfg

[linux-yocto] [yocto-kernel-cache][PATCH] vrf: Add feature

From: He Zhe Signed-off-by: He Zhe --- features/vrf/vrf.cfg | 4 features/vrf/vrf.scc | 4 2 files changed, 8 insertions(+) create mode 100644 features/vrf/vrf.cfg create mode 100644 features/vrf/vrf.scc diff --git a/features/vrf/vrf.cfg

[linux-yocto] [PATCH 1/2] fs/proc: kcore: use kcore_list type to check for vmalloc/module address

From: Ard Biesheuvel Instead of passing each start address into is_vmalloc_or_module_addr() to decide whether it falls into either the VMALLOC or the MODULES region, we can simply check the type field of the current kcore_list entry, since it will be set to

[linux-yocto] [PATCH 2/2] arm64: mm: select CONFIG_ARCH_PROC_KCORE_TEXT

From: Ard Biesheuvel To avoid issues with the /proc/kcore code getting confused about the kernels block mappings in the VMALLOC region, enable the existing facility that describes the [_text, _end) interval as a separate KCORE_TEXT region, which supersedes the

[linux-yocto] [PATCH] Revert mm/vmstat.c: fix vmstat_update() preemption BUG

From: Sebastian Andrzej Siewior commit 97731753d44d5efcb95b994dc952c0e8195b3e96 upstream This patch reverts commit c7f26ccfb2c3 ("mm/vmstat.c: fix vmstat_update() preemption BUG"). Steven saw a "using smp_processor_id() in preemptible" message and added a preempt_disable() section around it to

[linux-yocto] [PATCH] cfg: Add config fragments for docker

From: He Zhe Signed-off-by: He Zhe --- cfg/docker.cfg | 10 ++ cfg/docker.scc | 4 2 files changed, 14 insertions(+) create mode 100644 cfg/docker.cfg create mode 100644 cfg/docker.scc diff --git a/cfg/docker.cfg b/cfg/docker.cfg new file mode 100644 index 000..c678c94 ---

[linux-yocto] [PATCH] intel-x86: Add preemp-rt config entries

From: He Zhe Signed-off-by: He Zhe --- bsp/intel-x86/intel-x86-32-preempt-rt.scc | 9 + bsp/intel-x86/intel-x86-64-preempt-rt.scc | 8 2 files changed, 17 insertions(+) create mode 100644 bsp/intel-x86/intel-x86-32-preempt-rt.scc create mode 100644

[linux-yocto] [PATCH] rbd: Add fragments for Rados block device

From: He Zhe Signed-off-by: He Zhe --- cfg/rbd.cfg | 1 + cfg/rbd.scc | 4 2 files changed, 5 insertions(+) create mode 100644 cfg/rbd.cfg create mode 100644 cfg/rbd.scc diff --git a/cfg/rbd.cfg b/cfg/rbd.cfg new file mode 100644 index 000..156a099 --- /dev/null +++ b/cfg/rbd.cfg

[linux-yocto] [PATCH] netfilter: Fix kmemleak false positive reports

From: He Zhe unreferenced object 0x9643edb89900 (size 256): comm "sd-resolve", pid 220, jiffies 4295016710 (age 208.256s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 03 00 74 f3 ba b1 b6 b5 ..t. 65 3e 00 00 00 00 00 00 90 f9 a0 ed 43 96 ff ff e>..C...

[linux-yocto] [PATCH v2] ipv4: net namespace does not inherit network configurations

From: He Zhe patch from https://lkml.org/lkml/2014/7/29/119 Ipv4 net namespace requires a similar logic change as commit a79ca223e029 [ipv6: fix bad free of addrconf_init_net] introduces for newer kernels. Since a net namespace is independent to another. That is, there is no any relationship

[linux-yocto] [PATCH] ipv4: net namespace does not inherit network configurations

From: He Zhe patch from https://lkml.org/lkml/2014/7/29/119 Ipv4 net namespace requires a similar logic change as commit a79ca223e029 [ipv6: fix bad free of addrconf_init_net] introduces for newer kernels. Since a net namespace is independent to another. That is, there is no any relationship

[linux-yocto] [PATCH] kmemleak: Turn kmemleak_lock to raw spinlock on RT

From: He Zhe See https://lore.kernel.org/patchwork/patch/1011368/ for upstream status. kmemleak_lock, as a rwlock on RT, can possibly be held in atomic context and causes the follow BUG. BUG: scheduling while atomic: migration/15/132/0x0002 Modules linked in: iTCO_wdt iTCO_vendor_support

[linux-yocto] [PATCH] aufs: tiny, suppress a warning

From: "J. R. Okajima" commit 3a33601796d4139286c57cd15bf7d88d00aa7674 upstream Signed-off-by: J. R. Okajima fs/aufs/vdir.c: In function 'fillvdir': fs/aufs/vdir.c:493:15: warning: 'ino' may be used uninitialized in this function [-Wmaybe-uninitialized] arg->err = au_nhash_append_wh

[linux-yocto] [PATCH] powerpc: correct the preempt-lazy assembly

From: Sebastian Andrzej Siewior The powerpc port won't compile and abort with "Error: operand out of range" because the TIF_NEED_RESCHED_LAZY uses bit 20 which is larger than 15 which is the upper limit. Swap it with TIF_32BIT and fixup the assembly in one assembly file to get it to compile

[linux-yocto] [PATCH] powerpc: correct the preempt-lazy assembly

From: Sebastian Andrzej Siewior The powerpc port won't compile and abort with "Error: operand out of range" because the TIF_NEED_RESCHED_LAZY uses bit 20 which is larger than 15 which is the upper limit. Swap it with TIF_32BIT and fixup the assembly in one assembly file to get it to compile

[linux-yocto] [PATCH] Revert "igb: reduce CPU0 latency when updating statistics"

From: Jeff Kirsher This reverts commit 59361316afcb08569af21e1af83e89c7051c055a. Due to problems found in additional testing, this causes an illegal context switch in the RCU read-side critical section. CC: Dave Jones CC: Cong Wang CC: Jan Jablonsky Signed-off-by: Jeff Kirsher

[linux-yocto] [PATCH] serial: 8250: Fix serial8250 initialization crash

From: He Zhe https://lore.kernel.org/lkml/41c574bfdce7490597079dae8f328...@svr-chch-ex1.atlnz.lc/ The initialization code of interrupt backoff work might reference NULL pointer and cause the following crash, if no port was found. [ 10.017727] CPU 0 Unable to handle kernel paging request at

[linux-yocto] [PATCH] cgl: audit: Remove CONFIG_AUDIT_WATCH and CONFIG_AUDIT_WATCH

From: He Zhe In the following commits, these two options have been replaced by CONFIG_AUDITSYSCALL which is in audit.cfg. c8fc5d49c341 ("audit: remove WATCH and TREE config options") cb74ed278f80 ("audit: always enable syscall auditing when supported and audit is enabled") Signed-off-by: He

[linux-yocto] [PATCH] x86/resctrl: Rename INTEL_RDT to RESCTRL

From: He Zhe The following upstream commits have renamed INTEL_RDT to RESCTRL. 6fe07ce35e8a ("x86/resctrl: Rename the config option INTEL_RDT to RESCTRL") e6d429313ea5 ("x86/resctrl: Avoid confusion over the new X86_RESCTRL config") Signed-off-by: He Zhe --- bsp/intel-x86/intel-x86-64.cfg | 4

[linux-yocto] [PATCH] x86: lazy-preempt: use proper return label on 32bit-x86

From: Sebastian Andrzej Siewior The lazy-preempt uses the wrong return label in case preemption isn't possible. This results crash while returning to the kernel. Use the correct return label if preemption isn' possible. Reported-by: Andri Yngvason Signed-off-by: Sebastian Andrzej Siewior

[linux-yocto] [PATCH] ide: Fix ide convert to blk-mq

From: He Zhe This is written by Jens Axboe . https://lore.kernel.org/lkml/a0fcb119-82e7-c9b2-ea76-6aa39bd33...@windriver.com/ LTP case read_all_proc(read_all -d /proc -q -r 10) often, but not every time, fails with the following call traces, since 600335205b8d "ide: convert to blk-mq"(5.0-rc1)

[linux-yocto] [PATCH] samples: fix pidfd-metadata compilation

From: Guenter Roeck commit 7c33277b9a9ada187f805b41ffbebe6c51622fb6 upstream. Define __NR_pidfd_send_signal if it isn't to prevent a compilation error. To make pidfd-metadata compile on all arches, irrespective of whether or not syscall numbers are assigned, define the syscall number to -1. If

[linux-yocto] [PATCH] samples: fix pidfd-metadata compilation

From: Guenter Roeck Define __NR_pidfd_send_signal if it isn't to prevent a compilation error. To make pidfd-metadata compile on all arches, irrespective of whether or not syscall numbers are assigned, define the syscall number to -1. If it isn't defined this will cause the kernel to return

[linux-yocto] [PATCH] netfilter: Fix remainder of pseudo-header protocol 0

From: He Zhe Since v5.1-rc1, some types of packets do not get unreachable reply with the following iptables setting. Fox example, $ iptables -A INPUT -p icmp --icmp-type 8 -j REJECT $ ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. — 127.0.0.1 ping statistics — 1 packets

[linux-yocto] [PATCH] Revert "fuse: require /dev/fuse reads to have enough buffer capacity"

From: Miklos Szeredi This reverts commit d4b13963f217dd947da5c0cabd1569e914d21699. The commit introduced a regression in glusterfs-fuse. Reported-by: Sander Eikelenboom Signed-off-by: Miklos Szeredi --- This fixes failure to mount glusterfs and is from v5.2-rc6. If we're not going to merge

[linux-yocto] [PATCH] kmemleak: change the lock of kmemleak_object to raw_spinlock_t

From: Liu Haitao The following call trace would be triggered as kmemleak is running. BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:974 in_atomic(): 1, irqs_disabled(): 1, pid: 2401, name: kmemleak Preemption disabled at: [] scan_block+0x31/0x120 CPU: 12 PID:

[linux-yocto] [PATCH] tracing/x86: Fix compilation failure when CONFIG_TRACE_IRQFLAGS is off

From: He Zhe b470fb994ebd ("tracing/x86: Save CR2 before tracing irqsoff on error_entry") misses a "#ifdef". Signed-off-by: He Zhe --- arch/x86/entry/common.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/entry/common.c b/arch/x86/entry/common.c index 48a0a59..56d54d30 100644

[linux-yocto] [kernel-cache][PATCH] feature/net: Create a config variant of net.scc to for features

From: He Zhe Since b5776165c9d3 ("netfilter: Fix remainder of pseudo-header protocol 0"), net.scc includes a patch which would be reapplied when included by other features. This patches create a config variant net-enable.scc for features and leaves net.scc to BSPs as is. Signed-off-by: He Zhe

[linux-yocto] [kernel-cache][PATCH] features/security: Add more kernel hardening fragments

From: He Zhe Signed-off-by: He Zhe --- features/security/security.cfg | 16 1 file changed, 16 insertions(+) diff --git a/features/security/security.cfg b/features/security/security.cfg index 87408b6..8b7a065 100644 --- a/features/security/security.cfg +++

[linux-yocto] [PATCH v2] features/security: Add more kernel hardening fragments

From: He Zhe Signed-off-by: He Zhe --- v2: Add a note for people using uvesafb or other similar things. features/security/security.cfg | 18 ++ 1 file changed, 18 insertions(+) diff --git a/features/security/security.cfg b/features/security/security.cfg index 87408b6..0a4e246

  1   2   >