[PATCH] iio: adc: select buffer for at91-sama5d2_adc

We need to select the buffer code, otherwise we get build errors with undefined functions on the trigger and buffer, if we select just IIO and then AT91_SAMA5D2_ADC from menuconfig This adds a Kconfig 'select' statement like other ADC drivers have it already. Fixes: 5e1a1da0f8c9 ("iio: adc: at91-

Re: [PATCH 2/3] perf/buildid-cache: Support --list option

Thanks Jiri for the reviews. Will post v2 soon. -Ravi On 04/13/2018 06:28 PM, Jiri Olsa wrote: > On Mon, Apr 09, 2018 at 04:36:32PM +0530, Ravi Bangoria wrote: > > SNIP > >> - !remove_name_list_str && !purge_name_list_str && >> - !missing_filename && !update_name_l

[PATCH v2] mtd: onenand: omap2: Disable DMA for HIGHMEM buffers

dma_map_single doesn't get the proper DMA address for vmalloced area, so disable DMA in this case. Signed-off-by: Ladislav Michl Reported-by: "H. Nikolaus Schaller" Tested-by: "H. Nikolaus Schaller" --- Changes: -v2: Added Tested-by tag, based on v4.17-rc1 (no change in patch itself) driver

[tip:perf/urgent] perf annotate: Handle variables in 'sub', 'or' and many other instructions

Commit-ID: b0d5c81e872ed21de1e56feb0fa6e4161da7be61 Gitweb: https://git.kernel.org/tip/b0d5c81e872ed21de1e56feb0fa6e4161da7be61 Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 12 Apr 2018 16:28:18 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 13 Apr 2018 10:00:05 -0300 p

[tip:perf/urgent] perf annotate: Allow setting the offset level in .perfconfig

Commit-ID: 43c4023152a9c5742948ac919e58ade127fa4e2e Gitweb: https://git.kernel.org/tip/43c4023152a9c5742948ac919e58ade127fa4e2e Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 12 Apr 2018 15:23:02 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 13 Apr 2018 10:00:05 -0300 p

[tip:perf/urgent] perf report: Fix switching to another perf.data file

Commit-ID: 7b366142a50ad79e48de8e67c5b3e8cfb9fa82dd Gitweb: https://git.kernel.org/tip/7b366142a50ad79e48de8e67c5b3e8cfb9fa82dd Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 12 Apr 2018 14:58:24 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 13 Apr 2018 10:00:04 -0300 p

[PATCH] [PATCH v1] spi: cadence: Add usleep_range() for cdns_spi_fill_tx_fifo()

In case of xspi work in busy condition, may send bytes failed. once something wrong, spi controller did't work any more My test found this situation appear in both of read/write process. so when TX FIFO is full, add one byte delay before send data; Signed-off-by: sxauwsk Signed-off-by: guojian

[tip:perf/urgent] perf version: Print status for syscall_table

Commit-ID: 8a812bf552d98f6f887f860d3910f201b4a97b26 Gitweb: https://git.kernel.org/tip/8a812bf552d98f6f887f860d3910f201b4a97b26 Author: Jin Yao AuthorDate: Mon, 9 Apr 2018 18:26:49 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:33:34 -0300 perf version: Print

[tip:perf/urgent] perf record: Change warning for missing sysfs entry to debug

Commit-ID: 4f75f1cbf95e2f0853cd229d042b203931b899af Gitweb: https://git.kernel.org/tip/4f75f1cbf95e2f0853cd229d042b203931b899af Author: Thomas Richter AuthorDate: Thu, 12 Apr 2018 15:32:46 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 13 Apr 2018 09:59:56 -0300 perf record

[tip:perf/urgent] perf tests: Disable breakpoint accounting test for powerpc

Commit-ID: 4b163ca343b45855b03114ef2ab47c454989d55c Gitweb: https://git.kernel.org/tip/4b163ca343b45855b03114ef2ab47c454989d55c Author: Sandipan Das AuthorDate: Thu, 12 Apr 2018 21:51:40 +0530 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 14:20:21 -0300 perf tests: D

[tip:perf/urgent] perf sched: Fix documentation for timehist

Commit-ID: e8103e44cebe2ef891bc3a5c6c4b74854846968b Gitweb: https://git.kernel.org/tip/e8103e44cebe2ef891bc3a5c6c4b74854846968b Author: Takuya Yamamoto AuthorDate: Tue, 10 Apr 2018 23:35:39 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:33:36 -0300 perf sched

[tip:perf/urgent] Revert "x86/asm: Allow again using asm.h when building for the 'bpf' clang target"

Commit-ID: fd97d39b0aa49a4beb429aec344604c1b689f089 Gitweb: https://git.kernel.org/tip/fd97d39b0aa49a4beb429aec344604c1b689f089 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 11 Apr 2018 18:03:33 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:33:27 -0300 R

[tip:perf/urgent] perf tools: Rename HAVE_SYSCALL_TABLE to HAVE_SYSCALL_TABLE_SUPPORT

Commit-ID: 22e9af4e94801bbdf6945e55db64b877be7c71b3 Gitweb: https://git.kernel.org/tip/22e9af4e94801bbdf6945e55db64b877be7c71b3 Author: Jin Yao AuthorDate: Mon, 9 Apr 2018 18:26:48 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:33:31 -0300 perf tools: Rename

[tip:perf/urgent] perf tests bpf: Remove unused ptrace.h include from LLVM test

Commit-ID: c13009c1ef3a94cfea212c86bbb94c8361e5de0c Gitweb: https://git.kernel.org/tip/c13009c1ef3a94cfea212c86bbb94c8361e5de0c Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 11 Apr 2018 17:57:32 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:33:24 -0300 p

[tip:perf/urgent] perf annotate browser: Allow showing offsets in more than just jump targets

Commit-ID: 51f39603b5f260c73635f4d06d390476b32df6a5 Gitweb: https://git.kernel.org/tip/51f39603b5f260c73635f4d06d390476b32df6a5 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 11 Apr 2018 10:41:23 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:33:09 -0300 p

[tip:perf/urgent] perf annotate: Allow showing offsets in more than just jump targets

Commit-ID: 592c10e217f3edb35c7e0deba161fef69ad1a336 Gitweb: https://git.kernel.org/tip/592c10e217f3edb35c7e0deba161fef69ad1a336 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 11 Apr 2018 10:30:03 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:32:39 -0300 p

[tip:perf/urgent] perf jvmti: Give hints about package names needed to build

Commit-ID: e14b733c5dc62f574b4dbc045b2cc52b03d83d4c Gitweb: https://git.kernel.org/tip/e14b733c5dc62f574b4dbc045b2cc52b03d83d4c Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 11 Apr 2018 12:08:53 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 10:33:17 -0300 p

[tip:perf/urgent] perf stat: Enable 1ms interval for printing event counters values

Commit-ID: 9dc9a95f03a69ab926d9ff1986ab2087f34a5dce Gitweb: https://git.kernel.org/tip/9dc9a95f03a69ab926d9ff1986ab2087f34a5dce Author: Alexey Budankov AuthorDate: Tue, 3 Apr 2018 21:18:33 +0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 09:29:31 -0300 perf stat:

[tip:perf/urgent] perf tests: Run dwarf unwind test on arm32

Commit-ID: af72cfb80af5e4cafd8e0b58ac54f222c913aa1b Gitweb: https://git.kernel.org/tip/af72cfb80af5e4cafd8e0b58ac54f222c913aa1b Author: Kim Phillips AuthorDate: Tue, 10 Apr 2018 19:16:24 -0500 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 09:30:37 -0300 perf tests: R

[tip:perf/urgent] tools headers: Restore READ_ONCE() C++ compatibility

Commit-ID: 4d3b57da1593c66835d8e3a757e4751b35493fb8 Gitweb: https://git.kernel.org/tip/4d3b57da1593c66835d8e3a757e4751b35493fb8 Author: Mark Rutland AuthorDate: Wed, 4 Apr 2018 17:34:45 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 12 Apr 2018 09:30:09 -0300 tools headers:

[PATCH] Bluetooth: hci_qca: Avoid missing rampatch failure with userspace fw loader

AOSP use userspace firmware loader to load firmwares, which will return -EAGAIN in case qca/rampatch_00440302.bin is not found. Since there is no rampatch for dragonboard820c QCA controller revision, just make it work as is. CC: Loic Poulain CC: Nicolas Dechesne CC: Marcel Holtmann CC: Johan He

Re: [PATCH] efi: Fix the size not consistent issue when unmapping memory map

Hi Randy, On Mon, Apr 16, 2018 at 11:09:04AM +0800, Dave Young wrote: > On 04/16/18 at 10:57am, Dave Young wrote: > > On 04/13/18 at 02:27pm, Lee, Chun-Yi wrote: > > > When using kdump, SOMETIMES the "size not consistent" warning message > > > shows up when the crash kernel boots with early_iorema

Re: [PATCH] efi: Fix the size not consistent issue when unmapping memory map

On Mon, Apr 16, 2018 at 10:57:34AM +0800, Dave Young wrote: > On 04/13/18 at 02:27pm, Lee, Chun-Yi wrote: > > When using kdump, SOMETIMES the "size not consistent" warning message > > shows up when the crash kernel boots with early_ioremap_debug parameter: > > > > WARNING: CPU: 0 PID: 0 at ../mm/e

Re: [PATCH 4/5] dmaengine: sprd: Add Spreadtrum DMA configuration

On 16 April 2018 at 11:58, Vinod Koul wrote: > On Fri, Apr 13, 2018 at 02:41:48PM +0800, Baolin Wang wrote: >> On 13 April 2018 at 14:36, Vinod Koul wrote: >> > On Fri, Apr 13, 2018 at 02:17:34PM +0800, Baolin Wang wrote: >> > >> >> > Agreed, users only care about grabbing a channel, setting a de

Re: [PATCH] ARM: dts: da850: use gpio-ranges

On Monday 16 April 2018 12:27 AM, David Lechner wrote: > On 02/23/2018 05:44 AM, Sekhar Nori wrote: >> On Thursday 22 February 2018 09:04 PM, Linus Walleij wrote: >>> On Mon, Feb 19, 2018 at 11:29 PM, David Lechner >>> wrote: >>> This makes use of the gpio-ranges feature that connects GPIO >>

[PATCH v2 4/5] ALSA: xen-front: Implement handling of shared buffers

From: Oleksandr Andrushchenko Implement shared buffer handling according to the para-virtualized sound device protocol at xen/interface/io/sndif.h: - manage buffer memory - handle granted references - handle page directories Signed-off-by: Oleksandr Andrushchenko --- sound/xen/Makefile

[PATCH v2 0/5] ALSA: xen-front: Add Xen para-virtualized frontend driver

From: Oleksandr Andrushchenko Please note: this patch series depends on [3]. This patch series adds support for Xen [1] para-virtualized sound frontend driver. It implements the protocol from include/xen/interface/io/sndif.h with the following limitations: - mute/unmute is not supported - get/se

[PATCH v2 1/5] ALSA: xen-front: Introduce Xen para-virtualized sound frontend driver

From: Oleksandr Andrushchenko Introduce skeleton of the para-virtualized Xen sound frontend driver. Initial handling for Xen bus states: implement Xen bus state machine for the frontend driver according to the state diagram and recovery flow from sound para-virtualized protocol: xen/interface/io

Re: [RFC tip/locking/lockdep v6 01/20] lockdep/Documention: Recursive read lock detection reasoning

On Sat, Apr 14, 2018 at 05:38:54PM -0700, Randy Dunlap wrote: > Hi, > Hello Randy, > Just a few typos etc. below... > Thanks! I fixed those typos according to your comments. > On 04/11/2018 06:50 AM, Boqun Feng wrote: > > Signed-off-by: Boqun Feng > > --- > > Documentation/locking/lockdep-d

[PATCH v2 2/5] ALSA: xen-front: Read sound driver configuration from Xen store

From: Oleksandr Andrushchenko Read configuration values from Xen store according to xen/interface/io/sndif.h protocol: - introduce configuration structures for different components, e.g. sound card, device, stream - read PCM HW parameters, e.g rate, format etc. - detect stream type (cap

[PATCH v2 5/5] ALSA: xen-front: Implement ALSA virtual sound driver

From: Oleksandr Andrushchenko Implement essential initialization of the sound driver: - introduce required data structures - handle driver registration - handle sound card registration - register sound driver on backend connection - remove sound driver on backend disconnect Initialize

[PATCH v2 3/5] ALSA: xen-front: Implement Xen event channel handling

From: Oleksandr Andrushchenko Handle Xen event channels: - create for all configured streams and publish corresponding ring references and event channels in Xen store, so backend can connect - implement event channels interrupt handlers - create and destroy event channels with respe

Re: Wrong module .text address in 4.16.0

FWIW, this breaks at least perf capability to resolve module symbols. Adding some more CCs for perf and module. On 04/16/2018 07:51 AM, Thomas-Mich Richter wrote: > I just installed 4.16.0 and discovered the module .text address is > wrong. It happens on s390 and x86 platforms. I have not tested

Re: [PATCH 1/4] x86/crypto: camellia: Fix function prototypes

* Joao Moreira wrote: > Convert the use of 'struct camellia_ctx *' to 'void *' in prototypes of > functions which are referenced through 'struct common_glue_func_entry', > making their prototypes match those of this struct and, consequently, > turning them compatible with CFI requirements. > >

Re: instant reboot caused by 194a9749c73d650c0

* Eric Dumazet wrote: > Hi Kirill > > For some reason, my hosts instantly crash at boot time, with absolutely no > log on console. > > Bisection pointed to : > > $ git bisect bad > 194a9749c73d650c0b1dfdee04fb0bdf0a888ba8 is the first bad commit > commit 194a9749c73d650c0b1dfdee04fb0bdf0a888

Re: [PATCH v13 0/6] Address error and recovery for AER and DPC

On 2018-04-16 09:23, Sinan Kaya wrote: On 4/15/2018 11:16 PM, Bjorn Helgaas wrote: On Mon, Apr 09, 2018 at 10:41:48AM -0400, Oza Pawandeep wrote: This patch set brings in error handling support for DPC The current implementation of AER and error message broadcasting to the EP driver is tight

Re: [PATCH] x86/tools/relocs: comments cleanup

ping? On 03/05/2018 03:15 PM, Cao jin wrote: > 1. typo fix: there -> their > 2. remove superfluous "by" > > Signed-off-by: Cao jin > --- > arch/x86/tools/relocs.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/tools/relocs.c b/arch/x86/tools/relocs.c > in

KASAN: use-after-free Read in tipc_nametbl_stop

Hello, syzbot hit the following crash on net-next commit 5d1365940a68dd57b031b6e3c07d7d451cd69daf (Thu Apr 12 18:09:05 2018 +) Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=d64b64afc55660106556 So far this cras

Wrong module .text address in 4.16.0

I just installed 4.16.0 and discovered the module .text address is wrong. It happens on s390 and x86 platforms. I have not tested others. Here is the issue, I have used module qeth_l2 on s390 which is the ethernet device driver: root@s35lp76 ~]# lsmod Module Size Used by qeth_l2

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On 2018-04-16 11:03, p...@codeaurora.org wrote: On 2018-04-16 08:47, Bjorn Helgaas wrote: On Sat, Apr 14, 2018 at 11:53:17AM -0400, Sinan Kaya wrote: You indicated that you want to unify the AER and DPC behavior. Let's settle on what we want to do one more time. We have been going forth and ba

Re: [PATCH v13 6/6] PCI/DPC: Do not do recovery for hotplug enabled system

On 2018-04-16 08:47, Bjorn Helgaas wrote: On Sat, Apr 14, 2018 at 11:53:17AM -0400, Sinan Kaya wrote: You indicated that you want to unify the AER and DPC behavior. Let's settle on what we want to do one more time. We have been going forth and back on the direction. My thinking is that as muc

linux-next: Tree for Apr 16

Hi all, Changes since 20180413: The bpf tree gained a build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 379 366 files changed, 7652 insertions(+), 4560 deletions(-) I have create

Re: [PATCHv5] gpio: Remove VLA from gpiolib

On 16/04/2018 13:19, Phil Reid wrote: G'day Laura, One more comment. On 16/04/2018 12:41, Phil Reid wrote: G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a k

[PATCH] mailbox: arm_mhu: add support for mhuv2

ARM has launched a next version of MHU i.e. MHUv2 with its latest subsystems. The main change is that the MHUv2 is now a distributed IP with different peripheral views (registers) for the sender and receiver. Another main difference is that MHUv1 duplex channels are now split into simplex/half dup

Re: [PATCHv5] gpio: Remove VLA from gpiolib

G'day Laura, One more comment. On 16/04/2018 12:41, Phil Reid wrote: G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a kmalloc array is the easy way to fix thi

Re: [PATCH v4 08/15] KVM: s390: interfaces to (de)configure guest's AP matrix

Hi Tony, I love your patch! Yet something to improve: [auto build test ERROR on s390/features] [also build test ERROR on v4.17-rc1 next-20180413] [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/commits/

nds32 build failures

I thought I should give the brand new architecture a try. Unfortunately, that was not very successful. Build reference: v4.17-rc1 gcc version: nds32le-elf-gcc (GCC) 7.3.0 Building nds32:defconfig ... failed arch/nds32/include/asm/nds32.h: In function 'GIE_ENABLE': arch/nds32/include/asm/nds32.

Re: [linux-sunxi] [PATCH v2 00/10] Allwinner H3 DVFS support

On Mon, Apr 16, 2018 at 12:41 PM, Chen-Yu Tsai wrote: > Hi, > > On Tue, Feb 6, 2018 at 12:48 PM, Icenowy Zheng wrote: >> This patchset tries to add DVFS support for Allwinner H3 SoC, >> considering two kinds of adjustable regulators used on H3 boards: >> SY8106A I2C-controlled regulator and SY811

Re: [PATCHv5] gpio: Remove VLA from gpiolib

G'day Laura, On 14/04/2018 05:24, Laura Abbott wrote: The new challenge is to remove VLAs from the kernel (see https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla. Using a kmalloc array is the easy way to fix this but kmalloc is still more expensive than stack allocation. Introduce

Re: [linux-sunxi] [PATCH v2 00/10] Allwinner H3 DVFS support

Hi, On Tue, Feb 6, 2018 at 12:48 PM, Icenowy Zheng wrote: > This patchset tries to add DVFS support for Allwinner H3 SoC, > considering two kinds of adjustable regulators used on H3 boards: > SY8106A I2C-controlled regulator and SY8113B regulator (controllable > by GPIO with some special designs

Re: [PATCH v3 4/4] mm/sparse: Optimize memmap allocation during sparse_init()

On 04/14/2018 07:19 PM, Baoquan He wrote: >>> Yes, this place is the hardest to understand. The temorary arrays are >>> allocated beforehand with the size of 'nr_present_sections'. The error >>> paths you mentioned is caused by allocation failure of mem_map or >>> map_map, but whatever it's error o

Re: [PATCH v5 1/3] regulator: axp20x: add drivevbus support for axp803

On Thu, Apr 5, 2018 at 2:46 PM, Maxime Ripard wrote: > On Thu, Apr 05, 2018 at 12:11:39PM +0530, Jagan Teki wrote: >> On Tue, Mar 27, 2018 at 11:01 AM, Jagan Teki >> wrote: >> > Like axp221, axp223, axp813 the axp803 is also supporting external >> > regulator to drive the OTG VBus through N_VBU

Re: [PATCH] mtd: nand: mtk: use of_device_get_match_data()

On Mon, 2018-04-16 at 10:33 +0800, Ryder Lee wrote: > The usage of of_device_get_match_data() reduce the code size a bit. > > Also, the only way to call .probe() is to match an entry in > .of_match_table[], so of_device_id cannot be NULL. > > Signed-off-by: Ryder Lee > --- > drivers/mtd/nand/ra

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On (04/16/18 10:47), Sergey Senozhatsky wrote: > On (04/14/18 11:35), Sergey Senozhatsky wrote: > > On (04/13/18 10:12), Steven Rostedt wrote: > > > > > > > The interval is set to one hour. It is rather arbitrary selected time. > > > > It is supposed to be a compromise between never print these me

Re: [PATCH v4 4/4] zram: introduce zram memory tracking

On Sun, Apr 15, 2018 at 09:17:45PM -0700, Randy Dunlap wrote: > On 04/15/2018 08:31 PM, Minchan Kim wrote: > > zRam as swap is useful for small memory device. However, swap means > > those pages on zram are mostly cold pages due to VM's LRU algorithm. > > Especially, once init data for application

[PATCH] perf tools: set kernel end address properly

The map_groups__fixup_end() was called to set end addresses of kernel map and module maps. But now machine__create_modules() is set the end address of modules properly so the only remaining piece is the kernel map. We can set it with adjacent module's address directly instead of calling the map_g

[PATCH 05/25] staging: lustre: libcfs: remove excess space

From: Amir Shehata The function cfs_cpt_table_print() was adding two spaces to the string buffer. Just add it once. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http://review.whamcloud.com/18916 Reviewed-by: Olaf Weber Reviewed-by: Doug Ouch

[PATCH 02/22] staging: lustre: obd: create it_has_reply_body()

From: Vitaly Fertman The lookup_intent it_op fields in many cases will be compared to the settings of IT_OPEN | IT_UNLINK | IT_LOOKUP | IT_GETATTR. Create a simple inline function for this common case. Signed-off-by: Vitaly Fertman Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7433 Seagat

[PATCH 04/22] staging: lustre: ldlm: xattr locks are lost on mdt

From: Vitaly Fertman On the server side mdt_intent_getxattr() can return EFAULT if a buffer cannot be found, it is returned after lock_replace, where a new lock is installed into lockp. An error forces ldlm_lock_enqueue() to destroy the original lock, but ldlm_handle_enqueue0() drops the referenc

[PATCH 01/22] staging: lustre: llite: initialize xattr->xe_namelen

When the allocation of xattr->xe_name was moved to kstrdup() setting xattr->xe_namelen was dropped. This field is used in several parts of the xattr cache code so it broke xattr handling. Initialize xattr->xe_namelen when allocating xattr->xe_name succeeds. Also change the debugging statement to re

[PATCH 00/22] staging: lustre: llite: fix xattr handling

From: James Simmons Lustre utilities and user land APIs heavly depend on special xattr handling. Sadly much of the xattr handling for lustre client has been broken for awhile. This is all the fixes needed to make xattr handling work properly with the latest kernels. Bobi Jam (3): staging: lust

[PATCH 07/22] staging: lustre: llite: refactor lustre.lov xattr handling

From: Niu Yawei The function ll_xattr_set() contains special code to handle the lustre specific xattr lustre.lov. Move all this code to a new function ll_setstripe_ea(). Signed-off-by: Bobi Jam Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8998 Reviewed-on: https

[PATCH 05/22] staging: lustre: llite: handle xattr cache refill race

From: "John L. Hammond" In ll_xattr_cache_refill() if the xattr cache was invalid (and no request was sent) then return -EAGAIN so that ll_getxattr_common() caller will fetch the xattr from the MDT. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10132 Reviewe

[PATCH 10/22] staging: lustre: llite: return from ll_adjust_lum() if lump is NULL

From: Bobi Jam No need to check several times if lump is NULL. Just test once and return 0 if NULL. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9484 Reviewed-on: https://review.whamcloud.com/27126 Reviewed-by: Dmitry Eremin Reviewed-by: Niu Yawei Reviewed-by: J

Re: [PATCH v4 4/4] zram: introduce zram memory tracking

On 04/15/2018 08:31 PM, Minchan Kim wrote: > zRam as swap is useful for small memory device. However, swap means > those pages on zram are mostly cold pages due to VM's LRU algorithm. > Especially, once init data for application are touched for launching, > they tend to be not accessed any more and

[PATCH 03/22] staging: lustre: obd: change debug reporting in lmv_enqueue()

From: Vitaly Fertman Remove LL_IT2STR(it) from debug macros in lmv_enqueue(). The removal makes it possible to simplify the md_enqueue() functions. Signed-off-by: Vitaly Fertman Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7433 Seagate-bug-id: MRP-3072 MRP-3137 Reviewed-on: http://review

[PATCH 06/22] staging: lustre: llite: Remove filtering of seclabel xattr

From: Robin Humble The security.capability xattr is used to implement File Capabilities in recent Linux versions. Capabilities are a fine grained approach to granting executables elevated privileges. eg. /bin/ping can have capabilities cap_net_admin, cap_net_raw+ep instead of being setuid root.

[PATCH 09/22] staging: lustre: llite: break up ll_setstripe_ea function

From: Bobi Jam Place all the handling of information of trusted.lov that is not stripe related into the new function ll_adjust_lum(). Now ll_setstripe_ea() only handles striping information. Signed-off-by: Bobi Jam Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9484 Reviewed-on: https://re

[PATCH 14/22] staging: lustre: llite: record in stats attempted removal of lma/link xattr

Keep track of attempted deletions as well as changing of the lma/link xattrs. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin Reviewed-by: Bob Glossman Reviewed-by: Sebastien Buisson

[PATCH 12/22] staging: lustre: llite: fix invalid size test in ll_setstripe_ea()

The size check at the start of ll_setstripe_ea() is only valid for a directory. Move that check to the section of code handling the S_ISDIR case. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmit

[PATCH 08/22] staging: lustre: llite: add simple comment about lustre.lov xattrs

From: Niu Yawei Simple comment added to ll_xattr_set. Signed-off-by: Bobi Jam Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8998 Reviewed-on: https://review.whamcloud.com/24851 Reviewed-by: Andreas Dilger Reviewed-by: Lai Siyao Reviewed-by: Jinshan Xiong Signe

[PATCH 11/22] staging: lustre: llite: eat -EEXIST on setting trusted.lov

From: Bobi Jam Tools like rsync, tar, cp may copy and restore the xattrs on a file. The client previously ignored the setting of trusted.lov/lustre.lov if the layout had already been specified, to avoid causing these tools to fail for no reason. For PFL files we still need to silently eat -EEXIS

[PATCH 13/22] staging: lustre: llite: remove newline in fullname strings

In creating the full name of a xattr a new line was added that was seen by the remote MDS server which confused it. Remove the newline. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin

[PATCH 19/22] staging: lustre: llite: add support set_acl method in inode operations

From: Dmitry Eremin Linux kernel v3.14 adds set_acl method to inode operations. This patch adds support to Lustre for proper acl management. Signed-off-by: Dmitry Eremin Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamclou

[PATCH 20/22] staging: lustre: llite: use xattr_handler name for ACLs

From: "John L. Hammond" If struct xattr_handler has a name member then use it (rather than prefix) for the ACL xattrs. This avoids a bug where ACL operations failed for some kernels. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10785 Reviewed-on: https://re

[PATCH 18/22] staging: lustre: llite: style changes in xattr.c

Small style changes to match more the kernel code standard and it make it more readable. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by: Dmitry Eremin Reviewed-by: Bob Glossman Reviewed-by: Sebast

[PATCH 16/22] staging: lustre: llite: use proper types in the xattr code

Convert __uXX types to uXX types since this is kernel code. The function ll_lov_user_md_size() returns ssize_t so change lum_size from int to ssize_t. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27240 Reviewed-by:

[PATCH 17/22] staging: lustre: llite: cleanup xattr code comments

Add proper punctuation to the comments. Change buf_size to size for comment in ll_listxattr() since buf_size doesn't exit which will confuse someone reading the code. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9183 Reviewed-on: https://review.whamcloud.com/27

[PATCH 21/22] staging: lustre: llite: correct removexattr detection

In ll_xattr_set_common() detect the removexattr() case correctly by testing for a NULL value as well as XATTR_REPLACE. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10787 Reviewed-on: https://review.whamcloud.com/ Reviewed-by: Dmitry Eremin Reviewed-by: James

[PATCH 22/22] staging: lustre: llite: remove unused parameters from md_{get,set}xattr()

From: "John L. Hammond" md_getxattr() and md_setxattr() each have several unused parameters. Remove them and improve the naming or remaining parameters. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10792 Reviewed-on: https://review.whamcloud.com/ Reviewed-b

[PATCH 15/22] staging: lustre: llite: cleanup posix acl xattr code

Having an extra ifdef makes the code harder to read. For the case of ll_xattr_get_common() we have a variable initialized at the start of the function but it is only used in XATTR_ACL_ACCESS_T code block. Lets move that variable to that location since its only used there and make the code look clea

[PATCH 01/25] staging: lustre: libcfs: remove useless CPU partition code

From: Dmitry Eremin * remove scratch buffer and mutex which guard it. * remove global cpumask and spinlock which guard it. * remove cpt_version for checking CPUs state change during setup because of just disable CPUs state change during setup. * remove whole global struct cfs_cpt_data cpt_data.

[PATCH 03/25] staging: lustre: libcfs: implement cfs_cpt_cpumask for UMP case

From: Amir Shehata The function cfs_cpt_cpumask() exist for SMP systems but when CONFIG_SMP is disabled it only returns NULL. Fill in this missing function. Also properly initialize ctb_mask for the UMP case. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 R

[PATCH 06/25] staging: lustre: libcfs: replace num_possible_cpus() with nr_cpu_ids

From: Amir Shehata Move from num_possible_cpus() to nr_cpu_ids. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http://review.whamcloud.com/18916 Reviewed-by: Olaf Weber Reviewed-by: Doug Oucharek Signed-off-by: James Simmons --- drivers/sta

[PATCH 08/25] staging: lustre: libcfs: add cpu distance handling

From: Amir Shehata Add functionality to calculate the distance between two CPTs. Expose those distance in debugfs so people deploying a setup can debug what is being created for CPTs. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http://review

[PATCH 09/25] staging: lustre: libcfs: use distance in cpu and node handling

From: Amir Shehata Take into consideration the location of NUMA nodes and core when calling cfs_cpt_[un]set_cpu() and cfs_cpt_[un]set_node(). This enables functioning on platforms with 100s of cores and NUMA nodes. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-

[PATCH 11/25] staging: lustre: libcfs: invert error handling for cfs_cpt_table_print

From: Amir Shehata Instead of setting rc to -EFBIG for several cases in the loop lets initialize rc to -EFBIG and just break out of the loop in case of failure. Just set rc to zero once we successfully finish the loop. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse

[PATCH 04/25] staging: lustre: libcfs: replace MAX_NUMNODES with nr_node_ids

From: Amir Shehata Replace depricated MAX_NUMNODES with nr_node_ids. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http://review.whamcloud.com/18916 Reviewed-by: Olaf Weber Reviewed-by: Doug Oucharek Signed-off-by: James Simmons --- driver

[PATCH 14/25] staging: lustre: libcfs: rename i to node for cfs_cpt_set_nodemask

From: Dmitry Eremin Rename variable i to node to make code easier to understand. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23222 Reviewed-by: Amir Shehata Reviewed-by: James Simmons Reviewed-by: Oleg Drokin

[PATCH 10/25] staging: lustre: libcfs: provide debugfs files for distance handling

From: Amir Shehata On systems with large number of NUMA nodes and cores it is easy to incorrectly configure their use with Lustre. Provide debugfs files which can help track down any issues. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7734 Reviewed-on: http:/

[PATCH 02/25] staging: lustre: libcfs: rename variable i to cpu

From: Dmitry Eremin Change the name of the variable i used for for_each_cpu() to cpu for code readability. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23303 Reviewed-by: James Simmons Reviewed-by: Doug Oucharek

[PATCH 16/25] staging: lustre: libcfs: rename cpumask_var_t variables to *_mask

From: Dmitry Eremin Because we handle both cpu mask as well as core identifiers it can easily be confused. To avoid this rename various cpumask_var_t to have appended *_mask to their names. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https:

[PATCH 07/25] staging: lustre: libcfs: NUMA support

From: Amir Shehata This patch adds NUMA node support. NUMA node information is stored in the CPT table. A NUMA node mask is maintained for the entire table as well as for each CPT to track the NUMA nodes related to each of the CPTs. Add new function cfs_cpt_of_node() which returns the CPT of a pa

[PATCH 15/25] staging: lustre: libcfs: rename i to cpu for cfs_cpt_bind

From: Dmitry Eremin Rename variable i to cpu to make code easier to understand. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23222 Reviewed-by: Amir Shehata Reviewed-by: James Simmons Reviewed-by: Oleg Drokin

[PATCH 12/25] staging: lustre: libcfs: fix libcfs_cpu coding style

From: Dmitry Eremin This patch bring the lustre CPT code into alignment with the Linux kernel coding style. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23304 Reviewed-by: James Simmons Reviewed-by: Doug Ouchare

[PATCH 17/25] staging: lustre: libcfs: rename goto label in cfs_cpt_table_print

From: Dmitry Eremin Change goto label out to err. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23222 Reviewed-by: Amir Shehata Reviewed-by: James Simmons Reviewed-by: Oleg Drokin Signed-off-by: James Simmons

[PATCH 18/25] staging: lustre: libcfs: clear up failure patch in cfs_cpt_*_print

From: Dmitry Eremin Currently both cfs_cpt_table_print() and cfs_cpt_distance_print() handle the error path in a confusing way. Simplify it so it just returns E2BIG on failure instead of testing rc value before exiting. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/brow

[PATCH 21/25] staging: lustre: libcfs: report NUMA node instead of just node

From: Dmitry Eremin Reporting "HW nodes" is too generic. It really is reporting "HW NUMA nodes". Update the debug message. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23306 Reviewed-by: James Simmons Reviewed-b

[PATCH 13/25] staging: lustre: libcfs: use int type for CPT identification.

From: Dmitry Eremin Use int type for CPT identification to match the linux kernel CPU identification. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed-on: https://review.whamcloud.com/23304 Reviewed-by: James Simmons Reviewed-by: Doug Oucharek Rev

[PATCH 19/25] staging: lustre: libcfs: update debug messages

From: Dmitry Eremin For cfs_cpt_bind() change the CERROR to CDEBUG. Make the debug message in cfs_cpt_table_create_pattern() more understandable. Report rc value for when cfs_cpt_create_table() fails. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8703 Reviewed

  1   2   3   4   >