[PATCH 4.9 093/310] sched/numa: Use down_read_trylock() for the mmap_sem

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlastimil Babka [ Upstream commit 8655d5497735b288f8a9b458bd22e7d1bf95bb61 ] A customer has reported a soft-lockup when running an intensive memory stress test, where the

[PATCH 4.9 080/310] selftests/powerpc: Fix TM resched DSCR test with some compilers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman [ Upstream commit fe06fe860250a4f01d0eaf70a2563b1997174a74 ] The tm-resched-dscr test has started failing sometimes, depending on what compiler it's

[PATCH 4.9 082/310] ASoC: simple-card: fix mic jack initialization

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner [ Upstream commit f746aa5e8636c83e53bbb2d988bb614f732b2b80 ] Initialize asoc_simple_card_init_mic with the correct struct asoc_simple_jack. Fixes: 9eac361877b3

[PATCH 4.9 087/310] md-cluster: fix potential lock issue in add_new_disk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guoqing Jiang [ Upstream commit 2dffdc0724004f38f5e39907747b53e4b0d80e59 ] The add_new_disk returns with communication locked if __sendmsg returns failure, fix it with call

[PATCH 4.9 095/310] net/mlx5: Tolerate irq_set_affinity_hint() failures

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan [ Upstream commit b665d98edc9ab295169be2fc5bb4e89a46de0a1a ] Add tolerance to failures of irq_set_affinity_hint(). Its role is to give hints that optimizes

[PATCH 4.9 075/310] sh_eth: Use platform device for printing before register_netdev()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit 5f5c5449acad0cd3322e53e1ac68c044483b0aa5 ] The MDIO initialization failure message is printed using the network device, before it

[PATCH 4.9 098/310] mlx5: fix bug reading rss_hash_type from CQE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jesper Dangaard Brouer [ Upstream commit 12e8b570e732eaa5eae3a2895ba3fbcf91bde2b4 ] Masks for extracting part of the Completion Queue Entry (CQE) field rss_hash_type was

[PATCH 4.9 096/310] selinux: do not check open permission on sockets

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Smalley [ Upstream commit ccb544781d34afdb73a9a73ae53035d824d193bf ] open permission is currently only defined for files in the kernel (COMMON_FILE_PERMS rather

[PATCH 4.9 068/310] net: x25: fix one potential use-after-free issue

4.9-stable review patch. If anyone has any objections, please let me know. -- From: linzhang [ Upstream commit 64df6d525fcff1630098db9238bfd2b3e092d5c1 ] The function x25_init is not properly unregister related resources on error handler.It is will

[PATCH 4.9 224/310] perf tools: Decompress kernel module when reading DSO data

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Namhyung Kim [ Upstream commit 1d6b3c9ba756a5134fd7ad1959acac776d17404b ] Currently perf decompresses kernel modules when loading the symbol table but it missed to do it

[PATCH 4.9 228/310] X.509: Fix error code in x509_cert_parse()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 4e880168e9ffb1cdbdb72b3b48ab0324b30c2d62 ] We forgot to set the error code on this path so it could result in returning NULL which

[PATCH 4.9 212/310] nvme-pci: fix multiple ctrl removal scheduling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Rakesh Pandit [ Upstream commit 82b057caefaff2a891f821a617d939f46e03e844 ] Commit c5f6ce97c1210 tries to address multiple resets but fails as work_busy doesn't involve any

[PATCH 4.9 226/310] skbuff: only inherit relevant tx_flags

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit fff88030b3ff930ca7a3d74acfee0472f33887ea ] When inheriting tx_flags from one skbuff to another, always apply a mask to avoid overwriting

[PATCH 4.9 236/310] bnx2x: Allow vfs to disable txvlan offload

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Mintz, Yuval" [ Upstream commit 92f85f05caa51d844af6ea14ffbc7a786446a644 ] VF clients are configured as enforced, meaning firmware is validating the correctness of

[PATCH 4.9 222/310] Fix loop device flush before configure v3

4.9-stable review patch. If anyone has any objections, please let me know. -- From: James Wang [ Upstream commit 6460495709aeb651896bc8e5c134b2e4ca7d34a8 ] While installing SLES-12 (based on v4.4), I found that the installer will stall for 60+ seconds during

[PATCH 4.9 241/310] net: ena: fix rare uncompleted admin command false alarm

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Netanel Belgazal [ Upstream commit a77c1aafcc906f657d1a0890c1d898be9ee1d5c9 ] The current flow to detect admin completion is: while (command_not_completed) { if

[PATCH 4.9 232/310] stmmac: fix ptp header for GMAC3 hw timestamp

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mario Molitor [ Upstream commit fd6720aefde06eacf17404eed2cad65c6ec103e1 ] According the CYCLON V documention only the bit 16 of snaptypesel should set. (more

[PATCH 4.9 237/310] sctp: fix recursive locking warning in sctp_do_peeloff

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 6dfe4b97e08ec3d1a593fdaca099f0ef0a3a19e6 ] Dmitry got the following recursive locking report while running syzkaller fuzzer, the Call Trace:

[PATCH 4.9 308/310] strparser: Fix sign of err codes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Watson [ Upstream commit cd00edc179863848abab5cc5683de5b7b5f70954 ] strp_parser_err is called with a negative code everywhere, which then calls abort_parser with a

[PATCH 4.9 306/310] vhost_net: add missing lock nesting notation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit aaa3149bbee9ba9b4e6f0bd6e3e7d191edeae942 ] We try to hold TX virtqueue mutex in vhost_net_rx_peek_head_len() after RX virtqueue mutex is held

[PATCH 4.9 288/310] vhost: correctly remove wait queue during poll failure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit dc6455a71c7fc5117977e197f67f71b49f27baba ] We tried to remove vq poll from wait queue, but do not check whether or not it was in a list

[PATCH 4.9 289/310] vlan: also check phy_driver ts_info for vlans real device

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hangbin Liu [ Upstream commit ec1d8ccb07deaf30fd0508af6755364ac47dc08d ] Just like function ethtool_get_ts_info(), we should also consider the phy_driver ts_info call

[PATCH 4.9 310/310] vrf: Fix use after free and double free in vrf_finish_output

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern commit 82dd0d2a9a76fc8fa2b18d80b987d455728bf83a upstream. Miguel reported an skb use after free / double free in vrf_finish_output when neigh_output returns an

[PATCH 4.9 247/310] Bluetooth: Send HCI Set Event Mask Page 2 command only when needed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marcel Holtmann [ Upstream commit 313f6888c8fbb1bc8b36c9012ce4e1de848df696 ] The Broadcom BCM20702 Bluetooth controller in ThinkPad-T530 devices report support for the

[PATCH 4.9 253/310] vxlan: dont migrate permanent fdb entries during learn

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Roopa Prabhu [ Upstream commit e0090a9e979de5202c7d16c635dea2f005221073 ] This patch fixes vxlan_snoop to not move permanent fdb entries on learn events. This is

Re: [PATCH v2 09/13] locking/qspinlock: Merge struct __qspinlock into struct qspinlock

On 04/11/2018 02:01 PM, Will Deacon wrote: > struct __qspinlock provides a handy union of fields so that > subcomponents of the lockword can be accessed by name, without having to > manage shifts and masks explicitly and take endianness into account. > > This is useful in qspinlock.h and also

[PATCH 4.9 259/310] scsi: libsas: fix memory leak in sas_smp_get_phy_events()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Yan [ Upstream commit 4a491b1ab11ca0556d2fda1ff1301e862a2d44c4 ] We've got a memory leak with the following producer: while true; do cat

[GIT] Networking

1) In ip_gre tunnel, handle the conflict between TUNNEL_{SEQ,CSUM} and GSO/LLTX properly. From Sabrina Dubroca. 2) Stop properly on error in lan78xx_read_otp(), from Phil Elwell. 3) Don't uncompress in slip before rstate is initialized, from Tejaswi Tanikella. 4) When using 1.x firmware

[PATCH 10/20] staging: lustre: make struct lu_site_bkt_data private

This data structure only needs to be public so that various modules can access a wait queue to wait for object destruction. If we provide a function to get the wait queue, rather than the whole bucket, the structure can be made private. Signed-off-by: NeilBrown ---

[PATCH 11/20] staging: lustre: lu_object: discard extra lru count.

lu_object maintains 2 lru counts. One is a per-bucket lsb_lru_len. The other is the per-cpu ls_lru_len_counter. The only times the per-bucket counters are use are: - a debug message when an object is added - in lu_site_stats_get when all the counters are combined. The debug message is not

[PATCH 06/20] staging: lustre: ldlm: add a counter to the per-namespace data

When we change the resource hash to rhashtable we won't have a per-bucket counter. We could use the nelems global counter, but ldlm_resource goes to some trouble to avoid having any table-wide atomics, and hopefully rhashtable will grow the ability to disable the global counter in the near

[PATCH 15/20] staging: lustre: llite: use more private data in dump_pgcache

The dump_page_cache debugfs file allocates and frees an 'env' in each call to vvp_pgcache_start,next,show. This is likely to be fast, but does introduce the need to check for errors. It is reasonable to allocate a single 'env' when the file is opened, and use that throughout. So create

[PATCH 13/20] staging: lustre: lu_object: move retry logic inside htable_lookup

The current retry logic, to wait when a 'dying' object is found, spans multiple functions. The process is attached to a waitqueue and set TASK_UNINTERRUPTIBLE in htable_lookup, and this status is passed back through lu_object_find_try() to lu_object_find_at() where schedule() is called and the

[PATCH 14/20] staging: lustre: fold lu_object_new() into lu_object_find_at()

lu_object_new() duplicates a lot of code that is in lu_object_find_at(). There is no real need for a separate function, it is simpler just to skip the bits of lu_object_find_at() that we don't want in the LOC_F_NEW case. Signed-off-by: NeilBrown ---

[PATCH 18/20] staging: lustre: change how "dump_page_cache" walks a hash table

The "dump_page_cache" seq_file currently tries to encode a location in the hash table into a 64bit file index so that the seq_file can seek to any location. This is not necessary with the current implementation of seq_file. seq_file performs any seeks needed itself by rewinding and calling ->next

[PATCH 17/20] staging: lustre: use call_rcu() to free lu_object_headers

Using call_rcu to free lu_object_headers will allow us to use rhashtable and get lockless lookup. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/include/lu_object.h |6 +- drivers/staging/lustre/lustre/llite/vvp_object.c |9 -

[PATCH 16/20] staging: lustre: llite: remove redundant lookup in dump_pgcache

Both the 'next' and the 'show' functions for the dump_page_cache seqfile perform a lookup based on the current file index. This is needless duplication. The reason appears to be that the state that needs to be communicated from "next" to "show" is two pointers, but seq_file only provides for a

Re: [PATCH v3 09/10] drivers/hwmon: Add PECI hwmon client drivers

Hi Guenter, Thanks a lot for sharing your time. Please see my inline answers. On 4/10/2018 3:28 PM, Guenter Roeck wrote: On Tue, Apr 10, 2018 at 11:32:11AM -0700, Jae Hyun Yoo wrote: This commit adds PECI cputemp and dimmtemp hwmon drivers. Signed-off-by: Jae Hyun Yoo

Re: Q: Do si_time and si_utime need to be 64bit for y2038?

Arnd Bergmann writes: > On Wed, Apr 11, 2018 at 6:11 PM, Eric W. Biederman > wrote: >> >> Arnd, >> >> I am looking at the siginfo si_utime and si_stime fields of type clock_t >> on 32bit architectures except for x32 these are 32bit fields. For y2038 >> do

[PATCH V3] drm/amdgpu: limit DMA size to PAGE_SIZE for scatter-gather buffers

Code is expecing to observe the same number of buffers returned from dma_map_sg() function compared to sg_alloc_table_from_pages(). This doesn't hold true universally especially for systems with IOMMU. The hardware actually needs the dma_address on a page by page basis. Joining multiple

Re: [PATCH bpf-next v8 05/11] seccomp,landlock: Enforce Landlock programs per process hierarchy

On 04/10/2018 06:48 AM, Alexei Starovoitov wrote: > On Mon, Apr 09, 2018 at 12:01:59AM +0200, Mickaël Salaün wrote: >> >> On 04/08/2018 11:06 PM, Andy Lutomirski wrote: >>> On Sun, Apr 8, 2018 at 6:13 AM, Mickaël Salaün wrote: On 02/27/2018 10:48 PM, Mickaël Salaün

Re: AMD graphics performance regression in 4.15 and later

2018-04-11 20:35 GMT+02:00 Jean-Marc Valin : > On 04/11/2018 05:37 AM, Christian König wrote: >>> With your patches my EPYC box is unusable with 4.15++ kernels. >>> The whole Desktop is acting weird. This one is using >>> an Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]

Re: [PATCH] proc: fixup (c) sign

On Wed, Apr 11, 2018 at 1:24 PM, Alexey Dobriyan wrote: > > It got sent from here as iso8859-1. It's probably a good idea to just move away from Latin1 entirely, and encourage people to just use utf-8. But yes, Andrew's scripts clearly do a horrible job at looking at email

Re: [PATCH 4.4 000/190] 4.4.128-stable review

On 04/11/2018 12:34 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.128 release. > There are 190 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.9 000/310] 4.9.94-stable review

On 04/11/2018 12:32 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.94 release. > There are 310 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH v7 06/10] drm/dp_mst: Add reset_state callback to topology mgr

This gives drivers subclassing drm_dp_mst_topology_state the ability to prepare their topology states for a new hub to be connected whenever it's detected that the currently connected topology has been disconnected from the system. We'll need this in order to correctly track RX capabilities in

[PATCH v7 05/10] drm/dp_mst: Make drm_dp_mst_topology_state subclassable

This is useful for drivers (which will probably be all of them soon) which need to track state that is exclusive to the topology, and not a specific connector on said topology. This includes things such as the link rate and lane count that are shared by all of the connectors on the topology.

[PATCH v7 10/10] drm/i915: Implement proper fallback training for MST

For a while we actually haven't had any way of retraining MST links with fallback link parameters like we do with SST. While uncommon, certain setups such as my Caldigit TS3 + EVGA MST hub require this since otherwise, they end up getting stuck in an infinite MST retraining loop. MST retraining

[PATCH v7 09/10] drm/dp_mst: Add MST fallback retraining helpers

Unlike SST, MST can have far more then a single display hooked up on a single port. What this also means however, is that if the DisplayPort link to the top-level MST branch device becomes unstable then every single branch device also has an unstable link. Additionally, MST has a few more steps

[PATCH v7 03/10] drm/dp_mst: Fix naming on drm_atomic_get_mst_topology_state()

Since these functions are dealing with an atomic state that needs to be modified during atomic check and commit, change the naming on this function to drm_atomic_dp_mst_get_topology_state() since we're the only one using the function, and it's more consistent with the naming scheme used in

[PATCH v7 08/10] drm/i915: Make intel_dp_mst_atomic_check() idempotent

The current way of handling changing VCPI allocations doesn't make a whole ton of sense. Since drm_atomic_helper_check_modeset() can be called multiple times which means that intel_dp_mst_atomic_check() can also be called multiple times. However, since we make the silly mistake of trying to free

[PATCH v7 07/10] drm/i915: Only use one link bw config for MST topologies

When a DP MST link needs retraining, sometimes the hub will detect that the current link bw config is impossible and will update it's RX caps in the DPCD to reflect the new maximum link rate. Currently, we make the assumption that the RX caps in the dpcd will never change like this. This means if

[PATCH v7 02/10] drm/i915: Move DP modeset retry work into intel_dp

While having the modeset_retry_work in intel_connector makes sense with SST, this paradigm doesn't make a whole ton of sense when it comes to MST since we have to deal with multiple connectors. In most cases, it's more useful to just use the intel_dp struct since it indicates whether or not we're

[PATCH v7 01/10] drm/atomic: Print debug message on atomic check failure

Does what it says on the label, it's a little confusing debugging atomic check failures otherwise. Cc: Manasi Navare Cc: Ville Syrjälä Signed-off-by: Lyude Paul --- drivers/gpu/drm/drm_atomic.c | 5 - 1 file

[PATCH v7 00/10] drm/i915: Implement proper fallback training for MST

Next version of https://patchwork.freedesktop.org/series/41576/ All changes in this patch series are just to make checkpatch a little happier, no functional changes. Lyude Paul (10): drm/atomic: Print debug message on atomic check failure drm/i915: Move DP modeset retry work into intel_dp

[PATCH] Revert "perf machine: Fix paranoid check in machine__set_kernel_mmap()"

perf test 1 is failing on an arm64 box (that has a kernel module loaded fwiw). Running bisect resulted in commit 1d12cec6ce99 "perf machine: Fix paranoid check in machine__set_kernel_mmap()" being the first bad commit. Reverting it fixes symbol resolution: # ./perf.bad record true; ./perf.bad

[PATCH] dt-bindings: pinctrl: mcp23s08: Clarify gpiospec flags cell usage

The pinctrl-mcp23s08 driver doesn't provide a specific gpiospec of_xlate() function, causing the gpiolib-of's of_gpio_simple_xlate() function to be used instead, which takes the gpiospec's second cell as the flags specifier according to 'include/dt-bindings/gpio/gpio.h'. The pinctrl-mcp23s08

[PATCH 20/20] staging: lustre: remove cfs_hash resizeable hashtable implementation.

All users of this library have been converted to use rhashtable. Signed-off-by: NeilBrown --- .../staging/lustre/include/linux/libcfs/libcfs.h |1 .../lustre/include/linux/libcfs/libcfs_hash.h | 866 drivers/staging/lustre/lnet/libcfs/Makefile|2

[PATCH 19/20] staging: lustre: convert lu_object cache to rhashtable

The lu_object cache is a little more complex than the other lustre hash tables for two reasons. 1/ there is a debugfs file which displays the contents of the cache, so we need to use rhashtable_walk in a way that works for seq_file. 2/ There is a (shared) lru list for objects which are no

Re: [PATCH 2/3] ARM: dts: sun7i: Add RGB666 pins definition

Hi, Il 10/04/2018 23:31, Paul Kocialkowski ha scritto: This adds the pins definition for RGB666 LCD panels on the A20. It was imported from the A33 definition, that concernes the same set of pins. Signed-off-by: Paul Kocialkowski --- arch/arm/boot/dts/sun7i-a20.dtsi | 8

Re: [PATCH 01/24] Add the ability to lock down access to the running kernel image

On Wed, Apr 11, 2018 at 2:05 PM, Jordan Glover wrote: >> >> If that /dev/mem access prevention was just instead done as an even >> stricter mode of the existing CONFIG_STRICT_DEVMEM, it could just be >> enabled unconditionally. > > CONFIG_DEVMEM=n It's actually

[PATCH v7 04/10] drm/dp_mst: Remove all evil duplicate state pointers

There's no reason to track the atomic state three times. Unfortunately, this is currently what we're doing, and even worse is that there is only one actually correct state pointer: the one in mst_state->base.state. mgr->state never seems to be used, along with the one in mst_state->state. This

Re: [linux-sunxi] Re: [PATCH 2/3] ARM: dts: sun7i: Add RGB666 pins definition

Hi, Le jeudi 12 avril 2018 à 00:22 +0200, Giulio Benetti a écrit : > Hi, > > Il 10/04/2018 23:31, Paul Kocialkowski ha scritto: > > This adds the pins definition for RGB666 LCD panels on the A20. It > > was > > imported from the A33 definition, that concernes the same set of > > pins. > > > >

Re: [GIT PULL] asm-generic fixes for v4.17-rc1

On Wed, Apr 11, 2018 at 8:40 AM, Arnd Bergmann wrote: > > are available in the git repository at: > > > git+ssh://gitol...@ra.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git > tags/asm-generic Yeah, no they aren't available there at all. That tag is some old tag from

Re: [PATCH] sched/fair: schedutil: update only with all info available

Hi Vincent, On Wed, Apr 11, 2018 at 4:56 AM, Vincent Guittot wrote: > On 11 April 2018 at 12:15, Patrick Bellasi wrote: >> On 11-Apr 08:57, Vincent Guittot wrote: >>> On 10 April 2018 at 13:04, Patrick Bellasi wrote:

Re: [PATCH v5 1/1] security: Add mechanism to safely (un)load LSMs after boot time

On Wed, Apr 11, 2018 at 10:17 AM, Stephen Smalley wrote: > On 04/10/2018 05:24 PM, Sargun Dhillon wrote: >> On Sun, Apr 8, 2018 at 10:25 PM, Tetsuo Handa >> wrote: >>> Sargun Dhillon wrote: > Remove SECURITY_HOOK_COUNT and "struct

[PATCH 03/20] staging: lustre: convert obd uuid hash to rhashtable

The rhashtable data type is a perfect fit for the export uuid hash table, so use that instead of cfs_hash (which will eventually be removed). As rhashtable supports lookups and insertions in atomic context, there is no need to drop a spinlock while inserting a new entry, which simplifies code

[PATCH 02/20] staging: lustre: convert lov_pool to use rhashtable

The pools hashtable can be implemented using the rhashtable implementation in lib. This has the benefit that lookups are lock-free. We need to use kfree_rcu() to free a pool so that a lookup racing with a deletion will not access freed memory. rhashtable has no combined lookup-and-delete

[PATCH 04/20] staging: lustre: convert osc_quota hash to rhashtable

As this is indexed by an integer, an extensible array or extensible bitmap would be better. If/when xarray lands, we should change to use that. For now, just a simple conversion to rhashtable. When removing an entry, we need to hold rcu_read_lock() across the lookup and remove in case we race

[PATCH 01/20] staging: lustre: ptlrpc: convert conn_hash to rhashtable

Linux has a resizeable hashtable implementation in lib, so we should use that instead of having one in libcfs. This patch converts the ptlrpc conn_hash to use rhashtable. In the process we gain lockless lookup. As connections are never deleted until the hash table is destroyed, there is no need

[PATCH 07/20] staging: lustre: ldlm: store name directly in namespace.

Rather than storing the name of a namespace in the hash table, store it directly in the namespace. This will allow the hashtable to be changed to use rhashtable. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/include/lustre_dlm.h |5 -

[PATCH 09/20] staging: lustre: convert ldlm_resource hash to rhashtable.

Using an rhashtable allows lockless lookup at the cost of rcu freeing of entries. When we find an entry, we need to atomically check the reference hasn't dropped to zero. When adding an entry, we might find an existing entry which is in the process of being removed - with a zero refcount. In

[PATCH 00/20] staging: lustre: convert to rhashtable

libcfs in lustre has a resizeable hashtable. Linux already has a resizeable hashtable, rhashtable, which is better is most metrics. See https://lwn.net/Articles/751374/ in a few days for an introduction to rhashtable. This series converts lustre to use rhashtable. This affects several different

[PATCH 05/20] staging: lustre: separate buckets from ldlm hash table

ldlm maintains a per-namespace hashtable of resources. With these hash tables it stores per-bucket 'struct adaptive_timeout' structures. Presumably having a single struct for the whole table results in too much contention while having one per resource results in very little adaption. A future

[PATCH 08/20] staging: lustre: simplify ldlm_ns_hash_defs[]

As the ldlm_ns_types are dense, we can use the type as the index to the array, rather than searching through the array for a match. We can also discard nsd_hops as all hash tables now use the same hops. This makes the table smaller and the code simpler. Signed-off-by: NeilBrown

[PATCH 12/20] staging: lustre: lu_object: factor out extra per-bucket data

The hash tables managed by lu_object store some extra information in each bucket in the hash table. This prevents the use of resizeable hash tables, so lu_site_init() goes to some trouble to try to guess a good hash size. There is no real need for the extra data to be closely associated with

Re: usercopy whitelist woe in scsi_sense_cache

On Tue, Apr 10, 2018 at 8:13 PM, Kees Cook wrote: > I'll see about booting with my own kernels, etc, and try to narrow this down. > :) If I boot kernels I've built, I no longer hit the bug in this VM (though I'll keep trying). What compiler are you using? -Kees -- Kees

Re: [PATCH 3.18 000/121] 3.18.105-stable review

On 04/11/2018 12:35 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.105 release. > There are 121 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH v2] blk-cgroup: remove entries in blkg_tree before queue release

On Wed, Apr 11, 2018 at 09:28:30PM +, Bart Van Assche wrote: > On Wed, 2018-04-11 at 23:23 +0200, Alexandru Moise wrote: > > Hi, I tested it, it doesn't solve the problem. > > By the time you get here it's already too late, my patch > > prevents this from failing in the first place. > > Hello

Re: [PATCH 3/3] ARM: dts: sun7i: Add support for the Ainol AW1 tablet

Hi and thanks for the review ! Le mercredi 11 avril 2018 à 09:06 +0200, Maxime Ripard a écrit : > Hi, > > On Tue, Apr 10, 2018 at 11:31:29PM +0200, Paul Kocialkowski wrote: > > This adds support for the Ainol AW1, an A20-based 7" tablet from > > Ainol. > > > > The following board-specific

[PATCH 4.9 242/310] net: ena: fix race condition between submit and completion admin command

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Netanel Belgazal [ Upstream commit 661d2b0ccef6a63f48b61105cf7be17403d1db01 ] Bug: "Completion context is occupied" error printout will be noticed in dmesg. This error

[PATCH 4.9 213/310] nvme: fix hang in remove path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei [ Upstream commit 82654b6b8ef8b93ee87a97fc562f87f081fc2f91 ] We need to start admin queues too in nvme_kill_queues() for avoiding hang in remove path[1]. This

Re: [PATCH v2 2/2] slab: __GFP_ZERO is incompatible with a constructor

On Wed, Apr 11, 2018 at 08:44:23AM -0500, Christopher Lameter wrote: > > +++ b/mm/slub.c > > @@ -2725,7 +2726,7 @@ static __always_inline void *slab_alloc_node(struct > > kmem_cache *s, > > stat(s, ALLOC_FASTPATH); > > } > > > > - if (unlikely(gfpflags & __GFP_ZERO) && object) >

Re: [PATCH v2 04/13] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On 04/11/2018 02:01 PM, Will Deacon wrote: > The qspinlock locking slowpath utilises a "pending" bit as a simple form > of an embedded test-and-set lock that can avoid the overhead of explicit > queuing in cases where the lock is held but uncontended. This bit is > managed using a cmpxchg loop

Re: [PATCH 4.15 000/168] 4.15.17-stable review

On Wed, Apr 11, 2018 at 12:22:22AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.17 release. > There are 168 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

[PATCH 4.9 182/310] RDMA/iw_cxgb4: Avoid touch after free error in ARP failure handlers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Raju Rangoju [ Upstream commit 1dad0ebeea1cd890b8892523f736916e245b0aef ] The patch 761e19a504af (RDMA/iw_cxgb4: Handle return value of c4iw_ofld_send() in

Re: [PATCH] media: uvcvideo: Prevent setting unavailable flags

Hi Kieran, Thanks for the patch, it fixed a problem I was having with media master, working with a Logitech UVC 1.5 camera. On Wed, 21 Mar 2018, Kieran Bingham wrote: > The addition of an extra operation to use the GET_INFO command > overwrites all existing flags from the uvc_ctrls table. This

Re: [PATCH] sparc: compat: allow including asm/compat.h for 32-bit

Arnd Bergmann writes: > We have several files on sparc that include linux/compat.h and expect > asm/compat.h not to be included, otherwise we get a build failure. Should this say: "We have several files on sparc that include linux/compat.h and expect asm/compat.h not be included

Re: [PATCH] perf session: Fix undeclared 'oe'

On Wed, Apr 11, 2018 at 03:41:35PM -0300, Murilo Opsfelder Araujo wrote: > Using linux-3.18.y branch, perf build fails with the following: > > $ make -s -j16 -C tools/perf V=1 WERROR=0 NO_LIBUNWIND=1 > HAVE_CPLUS_DEMANGLE=1 NO_GTK2=1 NO_LIBNUMA=1 NO_STRLCPY=1 NO_BIONIC=1 > prefix=/usr

[PATCH 4.9 184/310] drm/omap: fix tiled buffer stride calculations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tomi Valkeinen [ Upstream commit cc8dd7661ccc2d8dc88921da8e6cc7c2fcdb0341 ] omap_gem uses page alignment for buffer stride. The related calculations are a bit off,

[PATCH 4.9 185/310] powerpc/8xx: fix mpc8xx_get_irq() return on no irq

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy [ Upstream commit 3c29b6038828c1f4c9ecbfec14d4fc5e25f1c947 ] IRQ 0 is a valid HW interrupt. So get_irq() shall return 0 when there is no irq, instead

[PATCH 4.9 139/310] vfb: fix video mode and line_length being set when loaded

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Pieter \\\"PoroCYon\\\" Sluys" [ Upstream commit 7b9faf5df0ac495a1a3d7cdb64921c179f9008ac ] Currently, when loading the vfb module, the newly created fbdev

[PATCH 4.9 189/310] ip6_tunnel: fix traffic class routing for tunnels

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liam McBirnie [ Upstream commit 5f733ee68f9a4df94775299ac6a7ab260704f6ed ] ip6_route_output() requires that the flowlabel contains the traffic class for policy routing.

[PATCH 4.9 154/310] dmaengine: imx-sdma: Handle return value of clk_prepare_enable

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arvind Yadav [ Upstream commit fb9caf370f4d0457789d13a1a1b110a8db846e5e ] clk_prepare_enable() can fail here and we must check its return value. Signed-off-by:

[PATCH 4.9 153/310] powerpc/[booke|4xx]: Dont clobber TCR[WP] when setting TCR[DIE]

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mikhaylov [ Upstream commit 6e2f03e292ef46eed2b31b0a344a91d514f9cd81 ] Prevent a kernel panic caused by unintentionally clearing TCR watchdog bits. At this point in the

Re: WARNING: possible recursive locking detected

Hello, On Wed, 11 Apr 2018, Dmitry Vyukov wrote: > On Wed, Apr 11, 2018 at 4:02 PM, syzbot > wrote: > > Hello, > > > > syzbot hit the following crash on upstream commit > > b284d4d5a6785f8cd07eda2646a95782373cd01e (Tue Apr 10

[PATCH 4.9 157/310] net/mlx5: avoid build warning for uniprocessor

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit f0d7ae95fff4ab444b8433f07afc4b077ef1a285 ] Building the driver with CONFIG_SMP disabled results in a harmless warning:

[PATCH 4.9 156/310] arm64: futex: Fix undefined behaviour with FUTEX_OP_OPARG_SHIFT usage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon [ Upstream commit 5f16a046f8e144c294ef98cd29d9458b5f8273e5 ] FUTEX_OP_OPARG_SHIFT instructs the futex code to treat the 12-bit oparg field as a shift value,

[PATCH 4.9 135/310] scsi: mpt3sas: Proper handling of set/clear of "ATA command pending" flag.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chaitra P B [ Upstream commit f49d4aed1315a7b766d855f1367142e682b0cc87 ] 1. In IO path, setting of "ATA command pending" flag early before device removal,

[PATCH 4.9 106/310] fix race in drivers/char/random.c:get_reg()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Schmitz [ Upstream commit 9dfa7bba35ac08a63565d58c454dccb7e1bb0a08 ] get_reg() can be reentered on architectures with prioritized interrupts (m68k in this case),

<    4   5   6   7   8   9   10   11   12   13   >