[PATCH 1/2] libnvdimm, label: change min label storage size per UEFI 2.7

UEFI 2.7 defines in page 758 that: Initial Label Storage Area Configuration : The minimum size of the Label Storage Area is large enough to hold 2 index blocks and 2 labels. The mininum index block size is 256 bytes, and the minimum label size is also 256 bytes. Change

[PATCH] selinux: fix typo in selinux_netlbl_sctp_sk_clone declaration

A missing 'struct' keyword caused a build error when CONFIG_NETLABEL is disabled: In file included from security/selinux/hooks.c:99: security/selinux/include/netlabel.h:135:66: error: unknown type name 'sock' static inline void selinux_netlbl_sctp_sk_clone(struct sock *sk, sock *newsk)

[PATCH 0/2] update label size handlings per UEFI 2.7

This patchset updates label storage size check and index block size calculation according to UEFI 2.7 spec. --- Toshi Kani (2): 1/2 libnvdimm, label: change min label storage size per UEFI 2.7 2/2 libnvdimm, label: change nvdimm_num_label_slots per UEFI 2.7 --- drivers/nvdimm/label.c | 34

Re: [PATCH] selinux: fix typo in selinux_netlbl_sctp_sk_clone declaration

On Fri, Feb 23, 2018 at 4:12 PM, Arnd Bergmann wrote: > A missing 'struct' keyword caused a build error when CONFIG_NETLABEL > is disabled: > > In file included from security/selinux/hooks.c:99: > security/selinux/include/netlabel.h:135:66: error: unknown type name 'sock' > static

Re: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap

On Wed, Feb 21, 2018 at 06:47:16PM +0100, KarimAllah Ahmed wrote: > ... since using kvm_vcpu_gpa_to_page() and kmap() will only work for guest > memory that has a "struct page". > > The life-cycle of the mapping also changes to avoid doing map and unmap on s/also changes/has been changed/ ?

Re: [PATCH v11 0/7] Address error and recovery for AER and DPC

On Fri, Feb 23, 2018 at 01:53:57PM +0530, 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 tightly coupled and limited to AER service driver. > It is important to factor out

Re: [PATCH 4.4 000/193] 4.4.118-stable review

On Fri, Feb 23, 2018 at 07:23:53PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.118 release. > There are 193 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] staging: gdm724x: hci: Remove unused struct sdu_header.

struct sdu_header isn't actually used anywhere in this driver, so this change removes it on the assumption it isn't needed for any API. Signed-off-by: Quytelda Kahja --- drivers/staging/gdm724x/hci_packet.h | 8 1 file changed, 8 deletions(-) diff --git

Re: [PATCH 9/9] scsi: ufs: Add clock ungating to a separate workqueue

On Wed, Feb 21, 2018 at 5:56 AM, Asutosh Das wrote: > From: Vijay Viswanath > > UFS driver can receive a request during memory reclaim by kswapd. > So when ufs driver puts the ungate work in queue, and if there are no > idle workers, kthreadd is

Re: [PATCH 4/7] Protectable Memory

On 2/23/18 6:48 AM, Igor Stoppa wrote: The MMU available in many systems running Linux can often provide R/O protection to the memory pages it handles. However, the MMU-based protection works efficiently only when said pages contain exclusively data that will not need further modifications.

[PATCH 1/3] rtc: pcf85363: add .max_register in regmap_config

This helps debugging as it allows reading registers from debugfs. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pcf85363.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/rtc/rtc-pcf85363.c b/drivers/rtc/rtc-pcf85363.c index

[rcu] 858c7b0986: BUG:KASAN:null-ptr-deref_in__lock_acquire

FYI, we noticed the following commit (built with gcc-7): commit: 858c7b0986b397d4960612f03a0ef00be69a8d3f ("rcu: Parallelize expedited grace-period initialization") https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev in testcase: trinity with following parameters:

The white man -- Who he is. A Discussion. (Removed by Youtube - Trying to squelch truth spoken to power)

www.liveleak.com/view?i=017_1519418755 This had to be reposted because the youtube people took down the video describing the truth about white society. Speaking truth to power isn't something they was fastioning to slide by. So, dear OpenSource folks, people that run the show on the

Re: [PATCH v11 8/8] perf: ARM DynamIQ Shared Unit PMU support

On 02/23/2018 03:35 AM, Mark Rutland wrote: On Thu, Feb 22, 2018 at 12:38:39PM -0800, Saravana Kannan wrote: On 02/22/2018 03:33 AM, Mark Rutland wrote: On Wed, Feb 21, 2018 at 06:32:46PM -0800, Saravana Kannan wrote: I'm not exactly sure if we can add entries to perf_type_id. If that's

[PATCH 4/5] selftests: size call ksft_print_header() to print TAP header

Call ksft_print_header() to print TAP header. This change helps prevent nested TAP headers when the test is run from run_tests and from script generated by emit_tests as in both of these cases KSFT_TAP_LEVEL will be set and ksft_print_header() will suppress the nested TAP header from size test.

[PATCH 5/5] selftests: futex Makefile add top level TAP header echo to RUN_TESTS

Add top level TAP header echo, testname and separator line to make the output consistent with the common run_tests target. Signed-off-by: Shuah Khan --- tools/testing/selftests/futex/Makefile | 3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH 2/5] selftests: lib.mk set KSFT_TAP_LEVEL to prevent nested TAP headers

Set KSFT_TAP_LEVEL before running tests to prevent nested TAP header printing from tests. Signed-off-by: Shuah Khan --- tools/testing/selftests/lib.mk | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/testing/selftests/lib.mk b/tools/testing/selftests/lib.mk

[PATCH 3/5] selftests: Makefile set KSFT_TAP_LEVEL to prevent nested TAP headers

Export KSFT_TAP_LEVEL and add TAP Header echo to the run_kselftest.sh script from emit_tests target handling. Signed-off-by: Shuah Khan --- tools/testing/selftests/Makefile | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git

Re: [v2,03/10] drm/sun4i: Protect the TCON pixel clocks

Il 21/02/2018 10:20, Maxime Ripard ha scritto: From: Maxime Ripard Both TCON clocks are very sensitive to clock changes, since any change might lead to improper timings. Make sure our rate is never changed. Signed-off-by: Maxime Ripard

Re: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap

On Fri, 2018-02-23 at 16:36 -0500, Konrad Rzeszutek Wilk wrote: > On Wed, Feb 21, 2018 at 06:47:16PM +0100, KarimAllah Ahmed wrote: > > > > ... since using kvm_vcpu_gpa_to_page() and kmap() will only work for guest > > memory that has a "struct page". > > > > The life-cycle of the mapping also

Re: [PATCH 4.14 000/159] 4.14.22-stable review

On Fri, Feb 23, 2018 at 07:25:08PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.22 release. > There are 159 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

Re: [PATCH v11 3/7] PCI/ERR: add mutex to synchronize recovery

On Fri, Feb 23, 2018 at 01:54:00PM +0530, Oza Pawandeep wrote: > This patch protects pci_do_recovery with mutex. pcie_do_recovery() Please explain why the mutex is necessary. What bad things happen without the mutex? You named (some) of the other things "pcie"; maybe use "pcie" in the mutex

Re: Kernel panic with 4.16-rc1 (and 4.16-rc2) running selftest

On Fri, Feb 23, 2018 at 3:27 PM, Cong Wang wrote: > On Fri, Feb 23, 2018 at 11:00 AM, Randy Dunlap wrote: >> [adding netdev] >> >> On 02/23/2018 08:05 AM, Khalid Aziz wrote: >>> I am seeing a kernel panic with 4.16-rc1 and 4.16-rc2 kernels when

[PATCH v1 2/2] perf/core: Add support for PMUs that can be read from any CPU

Some PMUs events can be read from any CPU. So allow the PMU to mark events as such. For these events, we don't need to reject reads or make smp calls to the event's CPU and cause unnecessary wake ups. Good examples of such events would be events from caches shared across all CPUs. Signed-off-by:

[PATCH v1 1/2] perf/core: Add API to look up PMU type by name

When the event numbers registered by multiple PMUs overlap, the attr->type value passed to perf_event_create_kernel_counter() is used to determine which PMU to use to create a perf_event. However, when the PMU in question is not a standard PMU (defined in perf_type_id), there is no way for a

Re: [PATCH] KVM: SVM: no need to call access_ok() in LAUNCH_MEASURE command

On 23/02/2018 19:36, Brijesh Singh wrote: > Using the access_ok() to validate the input before issuing the SEV > command does not buy us anything in this case. If userland is > giving us a garbage pointer then copy_to_user() will catch it when we try > to return the measurement. > > Suggested-by:

Re: [PATCH 4.9 000/145] 4.9.84-stable review

On 02/23/2018 11:25 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.84 release. > There are 145 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] KVM: x86: move LAPIC initialization after VMCS creation

On 24/02/2018 01:39, Liran Alon wrote: > I agree with the bug and the fix. > It makes sense to reset LAPIC in the same place other components are reset > rather than in it's creation. > > However, I failed to understand why you mention it fixes commit: > 851c1a18c541 ("KVM: nVMX: Fix injection to

[PATCH 02/12] bus: ti-sysc: Add suspend and resume handling

This allows us to idle the module on suspend after the children are suspended. Signed-off-by: Tony Lindgren --- drivers/bus/ti-sysc.c | 34 ++ 1 file changed, 34 insertions(+) diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c ---

[PATCH 00/12] Use dts data for ti-sysc to configure sysconfig

Hi all, This series of changes makes ti-sysc driver to use device tree data for configuring the interconnect target module registers. We already have smartreflex dts data configured according to the binding for ti-sysc, so that will be the first user. I've added code to check the dts data

[PATCH 03/12] bus: ti-sysc: Handle stdout-path for debug console

If we have stdout-path specified for earlycon, we must prevent the debug console from idling until runtime PM kicks in. Signed-off-by: Tony Lindgren --- drivers/bus/ti-sysc.c | 46 ++ 1 file changed, 46 insertions(+) diff --git

[PATCH 4/4] ARM: brcmstb: Add support for the V7 memory map

From: Doug Berger The 7278 device is the first device that includes support for the V7 memory map developed for use in 64-bit architecture brcmstb devices. This map relocates the register physical offset from 0xF000 to 0x0800. Since the ARM PERIPHBASE value is

[PATCH v5 2/2] dt/bindings: Add bindings for Layerscape external irqs

This adds Device Tree binding documentation for the external interrupt lines with configurable polarity present on some Layerscape SOCs. Signed-off-by: Rasmus Villemoes --- .../interrupt-controller/fsl,ls-extirq.txt | 44 ++ 1 file

[PATCH v5 0/2] irqchip: add support for Layerscape external interrupt lines

Changes since v4: - add SPDX license identifier to .c file - use 'reg' property to specify INTPCR register - use 'fsl,extirq-map' as property name for the mapping of interrupt numbers - rebase to v4.16-rc2 - change #interrupt-cells to 2 to avoid redundancy in interrupt specifiers Changes since

[PATCH 3/4] ARM: add Broadcom Brahma-B15 main ID definition

Define Broadcom's Brahma-B15 main ID register value, masked with ARM_CPU_PART_MASK. Signed-off-by: Florian Fainelli --- arch/arm/include/asm/cputype.h | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/include/asm/cputype.h b/arch/arm/include/asm/cputype.h index

[PATCH 1/4] ARM: Allow this header to be included by assembly files

From: Doug Berger The constants defined in this file are equally useful in assembly and C source files. The arm64 architecture version of this file allows inclusion in both assembly and C source files, so this this commit adds that capability to the arm architecture version so

[PATCH v0 1/3] livepatch: add sample cumulative patch

Add a simple atomic replace / cumulative livepatch example. Signed-off-by: Joe Lawrence --- samples/livepatch/Makefile | 1 + samples/livepatch/livepatch-cumulative.c | 216 +++ 2 files changed, 217 insertions(+) create mode

[PATCH v0 3/3] livepatch: update documentation for shadow variables

Update livepatch shadow variable documentation with respect to new atomic replace / cumulative patch functionality. Signed-off-by: Joe Lawrence --- Documentation/livepatch/shadow-vars.txt | 24 1 file changed, 24 insertions(+) diff --git

[PATCH v0 2/3] livepatch: update documentation/samples for callbacks

Update livepatch callback documentation and samples with respect to new atomic replace / cumulative patch functionality. Signed-off-by: Joe Lawrence --- Documentation/livepatch/callbacks.txt | 102 samples/livepatch/Makefile|

[PATCH v0 0/3] additional cumulative livepatch doc/samples

Hi Miroslav, This is a follow up to my comment on "Re: [PATCH v8 8/8] livepatch: Atomic replace and cumulative patches documentation". Here's what I was working on today, I can update for v9 and squash into a single patch or two if that fits into the patchset better. (Or Petr, feel free to grab

[PATCH 0.5/12] ARM: OMAP2+: Prepare to pass auxdata for smartreflex

We are still initializing smartreflex with platform data using omap_device_build(). We can instead pass the platform data in with auxdata in pdata-quirks.c and make the driver use that in later patches. Note that we cannot enable the auxdata use yet, this is done in the last patch of the series.

Re: [PATCH v12 10/11] sparc64: Add support for ADI (Application Data Integrity)

d test ERROR on v4.16-rc2] [cannot apply to next-20180222] [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/Khalid-Aziz/Application-Data-Integrity-feature-introduced-by-SPARC-M7/20180223-071725 base:

[PATCH 0/5] Handling for TAP header level

This patch series is a result discussion with Tim Bird about nested TAP header handling. Based on the discussion, I am introducing a environment variable to prevent nested TAP headers. These patches improve the run_tests output and the output from the script generated by emit_tests. This

[PATCH 1/5] selftests: kselftest framework: add handling for TAP header level

Introduce environment variable KSFT_TAP_LEVEL to avoid printing nested TAP headers for each test. lib.mk run_tests target prints TAP header before invoking the test program or test script. Tests need a way to suppress TAP headers if it is already printed out. This new environment variable adds a

[PATCH 01/10] iommu/amd: take into account that alloc_dev_data() may return NULL

find_dev_data() does not check whether the return value alloc_dev_data() is NULL. This was okay once because the pointer was returned once as-is. Since commit df3f7a6e8e85 ("iommu/amd: Use is_attach_deferred call-back") the pointer may be used within find_dev_data() so a NULL check is required.

[PATCH 10/10] iommu/amd: make amd_iommu_devtable_lock a spin_lock

Before commit 0bb6e243d7fb ("iommu/amd: Support IOMMU_DOMAIN_DMA type allocation") amd_iommu_devtable_lock had a read_lock() user but now there are none. In fact, after the mentioned commit we had only write_lock() user of the lock. Since there is no reason to keep it as writer lock, change its

[PATCH 09/10] iommu/amd: declare irq_remap_table's and amd_iommu's lock as a raw_spin_lock

The irq affinity setting is called while desc->lock is held. The desc->lock is a raw_spin_lock called with interrupts disabled. The call chain involves modify_irte_ga() which needs to take the irq_remap_table->lock in order to update the entry and later iommu->lock in order to update and flush the

Re: [PATCH 1/7] genalloc: track beginning of allocations

some code snipping . . . +/** + * get_bitmap_entry() - extracts the specified entry from the bitmap + * @map: pointer to a bitmap + * @entry_index: the index of the desired entry in the bitmap + * + * Return: The requested bitmap. + */ +static inline unsigned long get_bitmap_entry(unsigned long

[PATCH 03/10] iommu/amd: split domain id out of amd_iommu_devtable_lock

domain_id_alloc() and domain_id_free() is used for id management. Those two function share a bitmap (amd_iommu_pd_alloc_bitmap) and set/clear bits based on id allocation. There is no need to share this with amd_iommu_devtable_lock, it can use its own lock for this operation. Signed-off-by:

iommu/amd: lock splitting & GFP_KERNEL allocation

Hi, I have no idea why but suddenly my A10 box complained loudly about locking and memory allocations within the iommu code under RT. Looking at the code it has been like this for a longer time so the iommu must have appeared recently (well there was a bios upgrade due to other issues so it might

[PATCH 07/10] iommu/amd: factor out setting the remap table for a devid

Setting the IRQ remap table for a specific devid (or its alias devid) includes three steps. Those three steps are always repeated each time this is done. Introduce a new helper function, move those steps there and use that function instead. The compiler can still decide if it is worth to inline.

[PATCH 08/10] iommu/amd: drop the lock while allocating new irq remap table

The irq_remap_table is allocated while the iommu_table_lock is held with interrupts disabled. While this works it makes RT scream very loudly. >From looking at the call sites, all callers are in the early device initialisation (apic_bsp_setup(), pci_enable_device(), pci_enable_msi()) so make sense

Re: [PATCH 4.4 002/193] net: replace dst_cache ip6_tunnel implementation with the generic one

On Fri, Feb 23, 2018 at 07:23:55PM +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Paolo Abeni > > commit 607f725f6f7d5ec3759fbc16224afb60e2152a5b upstream. > > This also fix a

[v1 0/1] Allow deferred page initialization for xen pv

>From this discussion: https://www.spinics.net/lists/linux-mm/msg145604.html I investigated whether it is feasible to re-enable deferred page initialization on xen's para-vitalized domains. After studying the code, I found non-intrusive way to do just that. All we need to do is to assume that

[v1 1/1] xen, mm: Allow deferred page initialization for xen pv domains

Juergen Gross noticed that commit f7f99100d8d ("mm: stop zeroing memory during allocation in vmemmap") broke XEN PV domains when deferred struct page initialization is enabled. This is because the xen's PagePinned() flag is getting erased from struct pages when they are initialized later in boot.

response

I am Ms.Ella Golan, I am the Executive Vice President Banking Division with FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI). I am getting in touch with you regarding an extremely important and urgent matter. If you would oblige me the opportunity, I shall provide you with details upon your

Re: [PATCH v11 2/7] PCI/AER: factor out error reporting from AER

On Fri, Feb 23, 2018 at 01:53:59PM +0530, Oza Pawandeep wrote: > This patch factors out error reporting callbacks, which are currently > tightly coupled with AER. Add blank line between paragraphs. > DPC should be able to register callbacks and attmept recovery when DPC > trigger event occurs.

Re: [PATCH 4.4 000/193] 4.4.118-stable review

--- kernel: 4.4.118-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git tag: 4.4.118-rc1-hikey-20180223-139 git commit: 8cfc89f9b1c6bd4f522109f2a4f4baf7991070f8 git describe: 4.4.118-rc1-hikey-20180223-139 Test details: https://qa-reports.linaro.org/lkft/linar

Re: [PATCH v11 4/7] PCI/DPC: Unify and plumb error handling into DPC

On Fri, Feb 23, 2018 at 01:54:01PM +0530, Oza Pawandeep wrote: > Current DPC driver does not do recovery, e.g. calling end-point's driver's > callbacks, which sanitize the sw. > > DPC driver implements link_reset callback, and calls pcie_do_recovery. s/pcie_do_recovery/pcie_do_recovery()/ >

[PATCH 2/3] rtc: pcf85363: add alarm support

From: Alexandre Belloni Handle alarms, currently only on INTA Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-pcf85363.c | 159 + 1 file changed, 159 insertions(+)

[PATCH 3/3] rtc: pcf85363: set time accurately

As per 8.2.6 Setting and reading the time in RTC mode, first stop the clok, then reset it before setting the date and time registers. Finally, start the clock. This uses register address wrap around from 0x2f to 0x00 for efficiency. This allows to set the clock with a millisecond accuracy (drift

[PATCH] rtc: pcf85363: set time accurately

As per 8.2.6 Setting and reading the time in RTC mode, first stop the clok, then reset it before setting the date and time registers. Finally, start the clock. This uses register address wrap around from 0x2f to 0x00 for efficiency. This allows to set the clock with a millisecond accuracy (drift

Re: [PATCH 4.14 000/159] 4.14.22-stable review

On 02/23/2018 11:25 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.22 release. > There are 159 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.15 00/45] 4.15.6-stable review

On 02/23/2018 11:28 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.6 release. > There are 45 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 3.18 00/58] 3.18.96-stable review

On 02/23/2018 11:25 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.96 release. > There are 58 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 05/10] iommu/amd: remove the special case from get_irq_table()

get_irq_table() has a special ioapic argument. If set then it will pre-allocate / reserve the first 32 indexes. The argument is only once true and it would make get_irq_table() a little simpler if we would extract the special bits to the caller. Signed-off-by: Sebastian Andrzej Siewior

[PATCH 06/10] iommu/amd: use `table' instead `irt' as variable name in amd_iommu_update_ga()

The variable of type struct irq_remap_table is always named `table' except in amd_iommu_update_ga() where it is called `irt'. Make it consistent and name it also `table'. Signed-off-by: Sebastian Andrzej Siewior --- drivers/iommu/amd_iommu.c | 10 +- 1 file

[PATCH 02/10] iommu/amd: turn dev_data_list into a lock less list

alloc_dev_data() adds new items to dev_data_list and search_dev_data() is searching for items in this list. Both protect the access to the list with a spinlock. There is no need to navigate forth and back within the list and there is also no deleting of a specific item. This qualifies the list to

[PATCH 04/10] iommu/amd: split irq_lookup_table out of the amd_iommu_devtable_lock

The function get_irq_table() reads/writes irq_lookup_table while holding the amd_iommu_devtable_lock. It also modifies amd_iommu_dev_table[].data[2]. set_dte_entry() is using amd_iommu_dev_table[].data[0|1] (under the domain->lock) so it should be okay. The access to the iommu is serialized with

[PATCH v5 1/2] irqchip: add support for Layerscape external interrupt lines

The LS1021A allows inverting the polarity of six interrupt lines IRQ[0:5] via the scfg_intpcr register, effectively allowing IRQ_TYPE_LEVEL_LOW and IRQ_TYPE_EDGE_FALLING for those. We just need to check the type, set the relevant bit in INTPCR accordingly, and fixup the type argument before

Re: Avoid speculative indirect calls in kernel

Patchmeister Torvalds: "Or is Intel basically saying "we are committed to selling you shit forever and ever, and never fixing anything"?" Back in Celeron days, Intel was popular because you could clock the lesser cached Celeron 300mhz to ~500mhz. Everybody knew then not to get anything

Re: [PATCH v1 4/4] pci: Re-use new dmi_get_bios_year() helper

Please use PCI: Re-use ... to match the prevailing drivers/pci style. On Thu, Feb 22, 2018 at 02:59:23PM +0200, Andy Shevchenko wrote: > ...instead of open coding its functionality. Same comment about making the changelog complete, independent of the subject. > Signed-off-by: Andy

[4.9-stable PATCH 06/11] v4l2: disable filesystem-dax mapping support

commit b70131de648c2b997d22f4653934438013f407a1 upstream. V4L2 memory registrations are incompatible with filesystem-dax that needs the ability to revoke dma access to a mapping at will, or otherwise allow the kernel to wait for completion of DMA. The filesystem-dax implementation breaks the

[4.9-stable PATCH 08/11] libnvdimm, dax: fix 1GB-aligned namespaces vs physical misalignment

commit 41fce90f26333c4fa82e8e43b9ace86c4e8a0120 upstream. The following namespace configuration attempt: # ndctl create-namespace -e namespace0.0 -m devdax -a 1G -f libndctl: ndctl_dax_enable: dax0.1: failed to enable Error: namespace0.0: failed to enable failed to reconfigure

[4.9-stable PATCH 10/11] mm: fail get_vaddr_frames() for filesystem-dax mappings

commit b7f0554a56f21fb3e636a627450a9add030889be upstream. Until there is a solution to the dma-to-dax vs truncate problem it is not safe to allow V4L2, Exynos, and other frame vector users to create long standing / irrevocable memory registrations against filesytem-dax vmas.

[4.9-stable PATCH 07/11] IB/core: disable memory registration of filesystem-dax vmas

commit 5f1d43de54164dcfb9bfa542fcc92c1e1a1b6c1d upstream. Until there is a solution to the dma-to-dax vs truncate problem it is not safe to allow RDMA to create long standing memory registrations against filesytem-dax vmas. Link:

[4.9-stable PATCH 04/11] device-dax: implement ->split() to catch invalid munmap attempts

commit 9702cffdbf2129516db679e4467db81e1cd287da upstream. Similar to how device-dax enforces that the 'address', 'offset', and 'len' parameters to mmap() be aligned to the device's fundamental alignment, the same constraints apply to munmap(). Implement ->split() to fail munmap calls that

[4.9-stable PATCH 05/11] mm: introduce get_user_pages_longterm

commit 2bb6d2837083de722bfdc369cb0d76ce188dd9b4 upstream. Patch series "introduce get_user_pages_longterm()", v2. Here is a new get_user_pages api for cases where a driver intends to keep an elevated page count indefinitely. This is distinct from usages like iov_iter_get_pages where the

[4.9-stable PATCH 03/11] libnvdimm: fix integer overflow static analysis warning

commit 58738c495e15badd2015e19ff41f1f1ed55200bc upstream. Dan reports: The patch 62232e45f4a2: "libnvdimm: control (ioctl) messages for nvdimm_bus and nvdimm devices" from Jun 8, 2015, leads to the following static checker warning: drivers/nvdimm/bus.c:1018 __nd_ioctl()

[4.9-stable PATCH 02/11] fs/dax.c: fix inefficiency in dax_writeback_mapping_range()

From: Jan Kara commit 1eb643d02b21412e603b42cdd96010a2ac31c05f upstream. dax_writeback_mapping_range() fails to update iteration index when searching radix tree for entries needing cache flushing. Thus each pagevec worth of entries is searched starting from the start which is

[4.9-stable PATCH 01/11] mm: avoid spurious 'bad pmd' warning messages

From: Ross Zwisler commit d0f0931de936a0a468d7e59284d39581c16d3a73 upstream. When the pmd_devmap() checks were added by 5c7fb56e5e3f ("mm, dax: dax-pmd vs thp-pmd vs hugetlbfs-pmd") to add better support for DAX huge pages, they were all added to the end of if()

Re: [PATCH v3 0/2] KVM: MSR-based features

On 21/02/2018 20:39, Tom Lendacky wrote: > The following series implements support within KVM for MSR-based features. > The first patch creates the MSR-based feature framework used to retrieve > the available MSR-based features. The second patch makes use of the > framework to allow a guest to

Re: [PATCH 04/10] KVM: Introduce a new guest mapping API

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/KarimAllah-Ahmed/KVM-X86-Handle-guest-memory-that-does-not-have-a-struct-page/20180223-064826 > config: mips-malta_kvm_def

Re: [PATCH 2/3] power: supply: add cros-ec USB PD charger driver.

On Wed, Jan 17, 2018 at 6:59 PM, Enric Balletbo i Serra wrote: > From: Sameer Nanda > > This driver gets various bits of information about what is connected to > USB PD ports from the EC and converts that into power_supply properties. > >

Re: [BUG] lock_parent() breakage when used from shrink_dentry_list() (was Re: [PATCH v2 6/6] fs/dcache: Avoid remaining try_lock loop in shrink_dentry_list())

On Fri, Feb 23, 2018 at 01:35:52PM -0800, Linus Torvalds wrote: > This is too subtle, and your fix to check d_lockref.count < 0 sounds > wrong to me. If it's really gone, maybe it has been reused and the > refcount is positive again, but it's something else than a dentry > entirely? > > Hmm. >

Re: [PATCH] KVM: x86: move LAPIC initialization after VMCS creation

- pbonz...@redhat.com wrote: > The initial reset of the local APIC is performed before the VMCS has > been > created, but it tries to do a vmwrite: > > vmwrite error: reg 810 value 4a00 (err 18944) > CPU: 54 PID: 38652 Comm: qemu-kvm Tainted: GW I >

Re: [PATCH 4.4 000/193] 4.4.118-stable review

On 02/23/2018 11:23 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.118 release. > There are 193 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 2/4] ARM: add Broadcom Brahma-B53 main ID definition

From: Doug Berger This commit allows a Broadcom Brahma-B53 core to be detected when executing an arm architecture kernel in aarch32 state. Signed-off-by: Doug Berger Signed-off-by: Florian Fainelli --- arch/arm/include/asm/cputype.h

[PATCH 0/4] ARM: brcmstb: Add support for the V7 memory map

Hi all, This patch series updates the brcmstb.S DEBUG_LL routines to dynamically detect one of the latest STB chip: BCM7278. This chip has a different memory map which requires use to lookup the main ID register to know whether which register physical offset we must use. As a consequence of

[PATCH 2/2] libnvdimm, label: change nvdimm_num_label_slots per UEFI 2.7

sizeof_namespace_index() fails when NVDIMM devices have the minimum 1024 bytes label storage area. nvdimm_num_label_slots() returns 3 slots while the area is only big enough for 2 slots. Change nvdimm_num_label_slots() to calculate a number of label slots according to UEFI 2.7 spec.

Re: Removing architectures without upstream gcc support

On Fri, Feb 23, 2018 at 02:32:08PM -0500, James Bottomley wrote: > On Fri, 2018-02-23 at 18:19 +, Al Viro wrote: > [...] > > IIRC, parisc/qemu stuff had been announced a while ago; > > I have, but it didn't work sufficiently for me to either boot a kernel > using system emulation or start an

Re: [PATCH v1 1/4] dmi: Introduce dmi_get_bios_year() helper

On Thu, Feb 22, 2018 at 02:59:20PM +0200, Andy Shevchenko wrote: > It's used in several places and more users may come. > By using this helper they may create a slightly cleaner code. > > Signed-off-by: Andy Shevchenko > --- > include/linux/dmi.h | 7 +++ >

Re: [BUG] lock_parent() breakage when used from shrink_dentry_list() (was Re: [PATCH v2 6/6] fs/dcache: Avoid remaining try_lock loop in shrink_dentry_list())

On Fri, Feb 23, 2018 at 12:13 PM, Al Viro wrote: > Look: > dentry placed on a shrink list > we pick the fucker from the list and lock it. > we call lock_parent() on it. > dentry is not a root and it's not deleted, so we proceed. >

Re: [PATCH] PM / wakeirq: Add wakeup name to dedicated wake irqs

* Andy Shevchenko [180214 10:24]: > Subject: [PATCH] genirq: Add wakeup sysfs node to show IRQ wakeup state > > Surprisingly there is no simple way to see if the IRQ line in question > is wakeup source or not. Finally got around trying this one. Yeah it's nice and it

[4.9-stable PATCH 11/11] x86/entry/64: Clear extra registers beyond syscall arguments, to reduce speculation attack surface

commit 8e1eb3fa009aa7c0b944b3c8b26b07de0efb3200 upstream. At entry userspace may have (maliciously) populated the extra registers outside the syscall calling convention with arbitrary values that could be useful in a speculative execution (Spectre style) attack. Clear these registers to minimize

Re: [PATCHv5 0/5] Motorola Droid 4 Audio Support

* Sebastian Reichel [180223 20:03]: > Hi, > > This adds audio support to Motorola Droid 4. I dropped the > regulator from the DT binding as requested by Mark. Still works for me. Mark, are you happy now with the way the nodes are set up? For the binding and

[PATCH] KVM: x86: move LAPIC initialization after VMCS creation

The initial reset of the local APIC is performed before the VMCS has been created, but it tries to do a vmwrite: vmwrite error: reg 810 value 4a00 (err 18944) CPU: 54 PID: 38652 Comm: qemu-kvm Tainted: GW I 4.16.0-0.rc2.git0.1.fc28.x86_64 #1 Hardware name: Intel Corporation

Re: [PATCH 2/7] genalloc: selftest

+ locations[action->location] = gen_pool_alloc(pool, action->size); + BUG_ON(!locations[action->location]); Again, I'd think it through if you really want to use BUG_ON() or not: https://lwn.net/Articles/13183/ https://lkml.org/lkml/2016/10/4/1 Thanks, Jay

[PATCH v13 10/11] sparc64: Add support for ADI (Application Data Integrity)

ADI is a new feature supported on SPARC M7 and newer processors to allow hardware to catch rogue accesses to memory. ADI is supported for data fetches only and not instruction fetches. An app can enable ADI on its data pages, set version tags on them and use versioned addresses to access the data

Re: Kernel panic with 4.16-rc1 (and 4.16-rc2) running selftest

On Fri, Feb 23, 2018 at 11:00 AM, Randy Dunlap wrote: > [adding netdev] > > On 02/23/2018 08:05 AM, Khalid Aziz wrote: >> I am seeing a kernel panic with 4.16-rc1 and 4.16-rc2 kernels when running >> selftests >> from tools/testing/selftests. Last messages from selftest

  1   2   3   4   5   6   7   8   9   10   >