[PATCH] gpiolib: fix warning about iterator

We were getting build warning about "iterator" being used uninitialized. Use iterator properly to fix the build warning and in the process remove the variable "pos" which is not required now. Signed-off-by: Sudip Mukherjee --- drivers/gpio/gpiolib.c | 12 +--- 1 file changed, 5 insertion

Re: [PATCH v2] i2c-core: One function call less in acpi_i2c_space_handler() after error detection

> The kfree() function was called in one case by the > acpi_i2c_space_handler() function during error handling > even if the passed variable "client" contained a null pointer. This is OK. kfree() is known to be NULL-tolerant and we rely on it in various places to keep the code simpler. signatur

[PATCH v2] i2c-core: One function call less in acpi_i2c_space_handler() after error detection

From: Markus Elfring Date: Sat, 26 Dec 2015 08:00:52 +0100 The kfree() function was called in one case by the acpi_i2c_space_handler() function during error handling even if the passed variable "client" contained a null pointer. Implementation details could be improved by the adjustment of jump

[GIT PULL] ARC fixes for 4.4-rc7

Hi Linus, Sorry for this late pull request, but these are all important fixes for code introduced/updated in this release which we will otherwise end up back porting. Please pull and wish you happy holidays ! Thx, -Vineet ---> The following changes since commit 4ef7675344d687a0ef5b0d

Re: [PATCH] i2c-core: One function call less in acpi_i2c_space_handler() after error detection

[if your patch is applied to the wrong git tree, please drop us a note to help improving the system] Hi Markus, [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on v4.4-rc6 next-20151223] url: https://github.com/0day-ci/linux/commits/SF-Markus-Elfring/i2c-core-One-function-

[PATCH] i2c-core: One function call less in acpi_i2c_space_handler() after error detection

From: Markus Elfring Date: Sat, 26 Dec 2015 07:30:35 +0100 The kfree() function was called in one case by the acpi_i2c_space_handler() function during error handling even if the passed variable "client" contained a null pointer. Implementation details could be improved by the adjustment of jump

[PATCH] arm64: entry.S: add missing trace_hardirqs_off

Before calling schedule, we should trace hardirqs correctly. If not, we get following warning message when enabled CONFIG_DEBUG_LOCKDEP: [9.243073] DEBUG_LOCKS_WARN_ON(current->hardirqs_enabled) [ ... ] [9.262681] possible reason: unannotated irqs-off. [9.263018] irq event stamp: 25620

Hi

merry christmas dj,brand watch,doll,phone,tv,bike... the shipping is free,iphone6s, 368euro s ite: poazzlo. com

Re: [PATCH 3.2 46/77] drm: Fix an unwanted master inheritance v2

On Fri, 2015-12-25 at 15:13 +0100, Thomas Hellstrom wrote: > On 12/24/2015 04:37 PM, Ben Hutchings wrote: > > 3.2.75-rc1 review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: Thomas Hellstrom > > > > commit a0af2e538c80f3e47f1d6ddf120a153ad909

Re: [PATCH v3] um: Fix build error and kconfig for i386

On Fri, Dec 25, 2015 at 07:45:41PM +0100, Mickaël Salaün wrote: > > On 25/12/2015 02:34, Josh Triplett wrote: > > On Thu, Dec 24, 2015 at 01:12:11PM +0100, Mickaël Salaün wrote: > >> Fix build error by generating elfcore.o only when ELF_CORE (depending on > >> COREDUMP) is selected: > >> > >> arch

[PATCH] usb: gadget: acm: set notify_req to NULL after freed to avoid double free

From: "Du, Changbin" If acm_bind fails before allocate notification and acm->notify_req is not set to NULL after freed last time, double free will happen. kernel BUG at mm/slub.c:3392! invalid opcode: [#1] PREEMPT SMP EIP is at kfree+0x172/0x180 Call Trace: [<80c0e3b6>] ? usb_ep_autoconfig_

Re: [PATCH] null_blk: don't enable irqs when in irq

On 12/25/2015 07:26 AM, Rabin Vincent wrote: When using irq_mode=NULL_IRQ_TIMER, blk_start_queue() is called from the hrtimer interrupt. null_request_fn() calls spin_unlock_irq() and this causes the following splat from lockdep since interrupts are being enabled while we're in an interrupt handl

Re: [PATCH v4] pci: Limit VPD length for megaraid_sas adapter

Hi Bjorn, Checking again. How about adding some messages in the logs to let user know that vpd has been disabled on this device in case if there is an attempt to access vpd. What do you think?. Thanks Babu On 12/7/2015 5:07 PM, Babu Moger wrote: > Hi Bjorn, > My old logs were lost. So, I had t

linux-kernel antiblue protect eye for distributor

Dear linux-kernel MD, New LCD/LED TV defender blocker for year 2016. huge profits reserve for first distributor there, a lots request from end-users especial for antiblue protector. New and hottest model refer to http://www.emetal.tw/protect/p1-blue.htm inquire email to Eric from eMetal Techn

[PATCH] ptrace: being capable wrt a process requires mapped uids/gids

ptrace_has_cap() checks whether the current process should be treated as having a certain capability for ptrace checks against another process. Until now, this was equivalent to has_ns_capability(current, target_ns, CAP_SYS_PTRACE). However, if a root-owned process wants to enter a user namespace

[PATCH V2 1/1] Drivers: hv: vmbus: Add vendor and device atttributes

Add vendor and device attributes to VMBUS devices. These will be used by Hyper-V tools as well user-level RDMA libraries that will use the vendor/device tuple to discover the RDMA device. Signed-off-by: K. Y. Srinivasan --- V2: Addressed comments from Greg KH Documentation/ABI/stable/sy

Re: [PATCH] ptrace: being capable wrt a process requires mapped uids/gids

On Sat, Dec 12, 2015 at 09:12:41PM +0100, Jann Horn wrote: > With this change, the entering process can first enter the > namespace and then safely inspect the namespace's > properties, e.g. through /proc/self/{uid_map,gid_map}, > assuming that the namespace owner doesn't have access to > uid 0. A

Re: [PATCH v2 15/16] checkpatch: Add warning on deprecated walk_iomem_res

On Fri, 2015-12-25 at 15:09 -0700, Toshi Kani wrote: > Use of walk_iomem_res() is deprecated in new code.  Change > checkpatch.pl to check new use of walk_iomem_res() and suggest > to use walk_iomem_res_desc() instead. [] > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl [] > @@ -3424,6

[PATCH v2 5/6] watchdog: da9055_wdt: Drop reference counting

Reference counting is now implemented in the watchdog core and no longer required in watchdog drivers. Since it was implememented a no-op, and since the local memory is allocated with devm_kzalloc(), the reference counting code in the driver really did not really work anyway, and this patch effect

[PATCH v2 4/6] watchdog: da9052_wdt: Drop reference counting

Reference counting is now implemented in the watchdog core and no longer required in watchdog drivers. Since it was implememented a no-op, and since the local memory is allocated with devm_kzalloc(), the reference counting code in the driver really did not really work anyway, and this patch effect

[PATCH v2 3/6] watchdog: Separate and maintain variables based on variable lifetime

All variables required by the watchdog core to manage a watchdog are currently stored in struct watchdog_device. The lifetime of those variables is determined by the watchdog driver. However, the lifetime of variables used by the watchdog core differs from the lifetime of struct watchdog_device. To

[PATCH v2 0/6] watchdog: Replace driver based refcounting

All variables required by the watchdog core to manage a watchdog are currently stored in struct watchdog_device. The lifetime of those variables is determined by the watchdog driver. However, the lifetime of variables used by the watchdog core differs from the lifetime of struct watchdog_device. To

[PATCH v2 1/6] watchdog: Create watchdog device in watchdog_dev.c

The watchdog character device is currently created in watchdog_dev.c, and the watchdog device in watchdog_core.c. This results in cross-dependencies, since device creation needs to know the watchdog character device number as well as the watchdog class, both of which reside in watchdog_dev.c. Crea

[PATCH v2 6/6] hwmon: (sch56xx) Drop watchdog driver data reference count callbacks

Reference counting is now implemented in the watchdog core and no longer required in watchdog drivers. Signed-off-by: Guenter Roeck --- v2: Add missing kfree(). drivers/hwmon/sch56xx-common.c | 31 +-- 1 file changed, 1 insertion(+), 30 deletions(-) diff --git a/dri

[PATCH v2 2/6] watchdog: diag288: Stop re-using watchdog core internal flags

A watchdog driver should not use watchdog subsystem internal flags. Use a driver variable and flag instead to maintain the watchdog state and to determine if a suspend operation is possible or not. Signed-off-by: Guenter Roeck --- v2: Added patch drivers/watchdog/diag288_wdt.c | 26

[PATCH] ARM: dts: n900: Include adp1653 device

This patch adds adp1653 device into n900 DT structure. DT support in adp1653 driver is there since v4.2-rc1 version. Signed-off-by: Pali Rohár --- arch/arm/boot/dts/omap3-n900.dts | 15 +++ 1 file changed, 15 insertions(+) diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/b

[PATCH] Fix documentation for adp1653 DT

Property names do not match real names needed by driver itself. This patch fix this problem. Signed-off-by: Pali Rohár --- .../devicetree/bindings/media/i2c/adp1653.txt |7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/media/i2c/

[PATCH] ARM: dts: omap3: Include missing bandgap data for ti-soc-thermal driver

Driver for omap3 with documentation is there since v4.4-rc1. Signed-off-by: Pali Rohár --- arch/arm/boot/dts/omap34xx.dtsi |5 + arch/arm/boot/dts/omap36xx.dtsi |5 + 2 files changed, 10 insertions(+) diff --git a/arch/arm/boot/dts/omap34xx.dtsi b/arch/arm/boot/dts/omap34xx.dtsi

[PATCH] prism54: fix checks for dma mapping errors

prism54 checks for dma mapping errors by comparison returned address with zero, while pci_dma_mapping_error() should be used. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/net/wireless/prism54/islpci_dev.c | 4 +++- drivers/net/wire

[PATCH v2 01/16] resource: Add System RAM resource type

I/O resource type, IORESOURCE_MEM, is used for all types of memory-mapped ranges, ex. System RAM, System ROM, Video RAM, Persistent Memory, PCI Bus, PCI MMCONFIG, ACPI Tables, IOAPIC, reserved, and so on. This requires walk_system_ram_range(), walk_system_ram_res(), and region_intersects() to use

[PATCH v2 16/16] ACPI/EINJ: Allow memory error injection to NVDIMM

In the case of memory error injection, einj_error_inject() checks if a target address is System RAM. Change this check to allow injecting a memory error to NVDIMM by calling region_intersects() with IORES_DESC_PERSISTENT_MEMORY. This enables memory error testing on both System RAM and NVDIMM. In

[PATCH v2 02/16] resource: make resource flags handled properly

I/O resource flags consist of I/O resource types and modifier bits. Therefore, checking an I/O resource type in 'flags' must be performed with a bitwise operation. Fix find_next_iomem_res() and region_intersects() that simply compare 'flags' against a given value. Also change __request_region()

[PATCH v2 05/16] ia64: Set System RAM type and descriptor

Change efi_initialize_iomem_resources() to set 'flags' and 'desc' from EFI memory types. IORESOURCE_SYSRAM, a modifier bit, is set to 'flags' for System RAM as IORESOURCE_MEM is already set. IORESOURCE_SYSTEM_RAM is defined as (IORESOURCE_MEM|IORESOURCE_SYSRAM). I/O resource descritor is set to 'd

[PATCH v2 03/16] resource: Add I/O resource descriptor

walk_iomem_res() and region_intersects() still need to use strcmp() for searching a resource entry by @name in the iomem table. This patch introduces I/O resource descriptor, 'desc' in struct resoruce, for the iomem search interfaces. Drivers can assign their unique descritor to a range when they

[PATCH v2 06/16] arch: Set IORESOURCE_SYSTEM_RAM to System RAM

Set IORESOURCE_SYSTEM_RAM to 'flags' of resource ranges with "System RAM", "Kernel code", "Kernel data", and "Kernel bss". Note that: - IORESOURCE_SYSRAM (i.e. modifier bit) is set to 'flags' when IORESOURCE_MEM is already set. IORESOURCE_SYSTEM_RAM is defined as (IORESOURCE_MEM|IORESOURCE

[PATCH v2 09/16] drivers: Initialize resource entry to zero

I/O resource descriptor, 'desc' added to struct resource, needs to be initialized to zero by default. Some drivers call kmalloc() to allocate a resource entry, but does not initialize it to zero by memset(). Change these drivers to call kzalloc(), instead. Cc: linux-a...@vger.kernel.org Cc: linu

[PATCH v2 08/16] xen, mm: Set IORESOURCE_SYSTEM_RAM to System RAM

Set IORESOURCE_SYSTEM_RAM to 'flags' of struct resource entries with "System RAM". Cc: Andrew Morton Cc: Konrad Rzeszutek Wilk Cc: xen-de...@lists.xenproject.org Signed-off-by: Toshi Kani --- drivers/xen/balloon.c |2 +- mm/memory_hotplug.c |2 +- 2 files changed, 2 insertions(+), 2

[PATCH v2 07/16] kexec: Set IORESOURCE_SYSTEM_RAM to System RAM

Set IORESOURCE_SYSTEM_RAM to 'flags' and IORES_DESC_CRASH_KERNEL to 'desc' of "Crash kernel" resource ranges, which are child nodes of System RAM. Change crash_shrink_memory() to set IORESOURCE_SYSTEM_RAM for a System RAM range. Change kexec_add_buffer() to call walk_iomem_res() with IORESOURCE_S

[PATCH v2 10/16] resource: Change walk_system_ram to use System RAM type

Now that all System RAM resource entries have been initialized to IORESOURCE_SYSTEM_RAM type, change walk_system_ram_res() and walk_system_ram_range() to call find_next_iomem_res() by setting IORESOURCE_SYSTEM_RAM to @res.flags and NULL to @name. With this change, they walk through the iomem table

[PATCH v2 12/16] memremap: Change region_intersects() to take @flags and @desc

Change region_intersects() to identify a target with @flags and @desc, instead of @name with strcmp(). Change the callers of region_intersects(), memremap() and devm_memremap(), to set IORESOURCE_SYSTEM_RAM to @flags and IORES_DESC_NONE to @desc for searching System RAM. Also, export region_inter

[PATCH v2 13/16] resource: Add walk_iomem_res_desc()

Add a new interface, walk_iomem_res_desc(), which walks through the iomem table by identifying a target with @flags and @desc. This interface provides the same functionality as walk_iomem_res(), but does not use strcmp() to @name for better efficiency. walk_iomem_res() is deprecated, but is mainta

[PATCH v2 14/16] x86,nvdimm,kexec: Use walk_iomem_res_desc() for iomem search

Change to call walk_iomem_res_desc() for searching resource entries with the following names: "ACPI Tables" "ACPI Non-volatile Storage" "Persistent Memory (legacy)" "Crash kernel" Note, the caller of walk_iomem_res() with "GART" is left unchanged because this entry may be initialized by out-of

[PATCH v2 15/16] checkpatch: Add warning on deprecated walk_iomem_res

Use of walk_iomem_res() is deprecated in new code. Change checkpatch.pl to check new use of walk_iomem_res() and suggest to use walk_iomem_res_desc() instead. Cc: Andy Whitcroft Cc: Joe Perches Cc: Borislav Petkov Signed-off-by: Toshi Kani --- scripts/checkpatch.pl |6 ++ 1 file chan

[PATCH v2 04/16] x86/e820: Set System RAM type and descriptor

Change e820_reserve_resources() to set 'flags' and 'desc' from e820 types. IORESOURCE_SYSTEM_RAM is set to 'flags' for System RAM, which are E820_RESERVED_KERN and E820_RAM. IORESOURCE_SYSTEM_RAM is also set to "Kernel data", "Kernel code", and "Kernel bss", which are children nodes of System RAM

[PATCH v2 11/16] arm/samsung: Change s3c_pm_run_res() to use System RAM type

Change s3c_pm_run_res() to check with IORESOURCE_SYSTEM_RAM, instead of strcmp() with "System RAM", to walk through System RAM ranges in the iomem table. No functional change is made to the interface. Cc: Krzysztof Kozlowski Cc: linux-samsung-...@vger.kernel.org Reviewed-by: Krzysztof Kozlowski

[PATCH v2 00/16] Enhance iomem search interfaces and support EINJ to NVDIMM

This patch-set enhances the iomem table and its search interfacs, and then changes EINJ to support NVDIMM. - Patches 1-2 add a new System RAM type, IORESOURCE_SYSTEM_RAM, and make the iomem search interfaces work with resource flags with modifier bits set. IORESOURCE_SYSTEM_RAM has IORESOU

Re: [PATCHV5 3/3] x86, ras: Add __mcsafe_copy() function to recover from machine checks

mce_in_kernel_recov() should check whether we have a fix up entry for the specific IP that hit the machine check before rating the severity as kernel recoverable. If we add more functions (for different cache behaviour, or to optimize for specific processor model) we can make sure to put them a

Re: [PATCH v3] um: Fix build error and kconfig for i386

On 25/12/2015 02:34, Josh Triplett wrote: > On Thu, Dec 24, 2015 at 01:12:11PM +0100, Mickaël Salaün wrote: >> Fix build error by generating elfcore.o only when ELF_CORE (depending on >> COREDUMP) is selected: >> >> arch/x86/um/built-in.o: In function `elf_core_write_extra_phdrs': >> (.text+0x3e62

[PATCH] gpio-ucb1400: Delete an unnecessary variable initialisation in ucb1400_gpio_probe()

From: Markus Elfring Date: Fri, 25 Dec 2015 19:36:20 +0100 The variable "err" will eventually be set to an appropriate value from a call of the gpiochip_add() function. Thus let us omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring --- drivers/gpio/gpio-ucb1400.c

sata_mv: Another source code review around exception handling?

Hello, I have looked at the source file for the Marvell SATA support driver once more. I would appreciate if a specific implementation detail can be clarified there. Static source code analysis can point out that functions like the following are called by the mv_platform_probe() function. https:/

Re: [PATCH v2] um: Fix build error and kconfig for i386

Am 25.12.2015 um 02:26 schrieb Josh Triplett: > On Thu, Dec 24, 2015 at 01:09:45PM +0100, Mickaël Salaün wrote: >> >> On 23/12/2015 22:42, Josh Triplett wrote: >>> On Wed, Dec 23, 2015 at 01:59:13PM +0100, Mickaël Salaün wrote: Fix build error by selecting COREDUMP when X86_32 is selected: >>>

[PATCH] null_blk: don't enable irqs when in irq

When using irq_mode=NULL_IRQ_TIMER, blk_start_queue() is called from the hrtimer interrupt. null_request_fn() calls spin_unlock_irq() and this causes the following splat from lockdep since interrupts are being enabled while we're in an interrupt handler. When we're in null_request_fn() we can't k

Re: [PATCH 3.2 46/77] drm: Fix an unwanted master inheritance v2

On 12/24/2015 04:37 PM, Ben Hutchings wrote: > 3.2.75-rc1 review patch. If anyone has any objections, please let me know. > > -- > > From: Thomas Hellstrom > > commit a0af2e538c80f3e47f1d6ddf120a153ad909e8ad upstream. > > A client calling drmSetMaster() using a file descriptor tha

Re: [PATCH] crypto: ccp - use to_pci_dev and to_platform_device

On Wed, Dec 23, 2015 at 08:49:01PM +0800, Geliang Tang wrote: > Use to_pci_dev() and to_platform_device() instead of open-coding. > > Signed-off-by: Geliang Tang Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~he

Re: [PATCH] ARM: omapfb: Add early framebuffer memory allocator

On 26.12.2013 01:12, Ivaylo Dimitrov wrote: From: Ivaylo Dimitrov On memory limited devices, CMA fails easily when asked to allocate big chunks of memory like framebuffer memory needed for video playback. Add boot parameter "omapfb_memsize" which allocates memory to be used as dma coherent mem

Re: [PATCH v2] ARM: OMAPFB: panel-sony-acx565akm: fix missing mutex unlocks

Hi Tomi, On 13.01.2014 12:20, Tomi Valkeinen wrote: On 2014-01-11 11:39, Ivaylo Dimitrov wrote: The patch does not apply cleanly on top of rc7, however I applied it by hand. So far it seems it fixes the issue brought by c37dd677988ca50bc8bc60ab5ab053720583c168, though I didn't test if mutex_l

Re: [PATCH 0/2] two fixes for new bq27000/10 and bq27500 driver

On Thursday 24 December 2015 14:57:56 Andrew F. Davis wrote: > > Also I wonder if you would be available as official reviewer for > > the driver. > > Sure, what's the normal procedure for this, should I submit a > patch adding myself to that driver in MAINTAINERS? Yes, send patch. -- Pali Rohá

Re: [PATCH 1/2] power:bq27xxx: fix reading for bq27000 and bq27010

On Thursday 17 December 2015 11:12:53 H. Nikolaus Schaller wrote: > bug: the driver reports funny capacity values: > > root@letux:/sys/class/power_supply/bq27000-battery# cat uevent > POWER_SUPPLY_NAME=bq27000-battery > POWER_SUPPLY_STATUS=Charging > POWER_SUPPLY_PRESENT=1 > POWER_SUPPLY_VOLTAGE_N

Re: [PATCH 1/2] dell-wmi: Check if Dell WMI descriptor structure is valid

On Friday 25 December 2015 02:23:04 Andy Lutomirski wrote: > On Thu, Dec 24, 2015 at 1:18 PM, Pali Rohár > wrote: > > According to Dell WMI document mentioned in ML dicussion archived > > at http://www.spinics.net/lists/platform-driver-x86/msg07220.html > > OS should check Dell WMI descriptor stru

Re: [PATCH v12 16/18] drm: bridge: analogix/dp: expand the wait time for looking AUX CH reply flag

On Thursday, December 24, 2015 10:23 AM, Yakir Yang wrote: > > Hi Jingoo, > > Okay, fine, I would drop this patch, until I found the the root cause. OK, I see. Best regards, Jingoo Han > > - Yakir > > On 12/23/2015 11:10 PM, Jingoo Han wrote: > > On Wednesday, December 23, 2015 9:51 PM, Yaki

Re: mmc does not work in qemu n900

On Monday 26 January 2015 22:04:59 Pali Rohár wrote: > Hello, > > for unknown reason kernel in qemu n900 machine is not able to > detect internal eMMC memory. External SD card is detected without > problem. > > If I apply this one-line patch eMMC in qemu start working: > > diff --git a/drivers/m

Re: [PATCH 1/2] mmc: omap_hsmmc: Add support for slot-name property in DT

On Monday 18 May 2015 17:07:57 Arnd Bergmann wrote: > On Monday 18 May 2015 08:06:07 Tony Lindgren wrote: > > * Arnd Bergmann [150515 14:26]: > > > On Friday 15 May 2015 23:22:37 Pali Rohár wrote: > > If setting up the generic binding is expected to take a while, > > you can naturally pass it in p

[PATCH] pinctrl: qcom: make PMIC drivers bool

commit ab4256cfeab91569e1d96e7f0014538fe0845259 "pinctrl: qcom: pmic-gpio/mpp: of_irq_count() == npins" made the Qualcomm PMIC pin control drivers make use of of_irq_count() which is not an exported function, making modular builds fail. Fix this by marking the drivers as compiled-in/bool. Cc: Ste

[GIT PULL] parisc syscall restart fix for v4.4

Hi Linus, please pull one late patch for the parisc architecture for kernel v4.4 from: git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.4-4 The architectural design of parisc always uses two instructions to call kernel syscalls (delayed branch feature). This mean

Re: [PATCHV5 3/3] x86, ras: Add __mcsafe_copy() function to recover from machine checks

On Tue, Dec 15, 2015 at 05:30:49PM -0800, Tony Luck wrote: > Using __copy_user_nocache() as inspiration create a memory copy > routine for use by kernel code with annotations to allow for > recovery from machine checks. > > Notes: > 1) We align the source address rather than the destination. This

Re: [PATCH 1/2] mm, oom: introduce oom reaper

On Fri 25-12-15 12:35:37, Michal Hocko wrote: [...] > Thanks I will try to reproduce early next year. But so far I think this > is just a general issue of MADV_DONTNEED vs. truncate and oom_reaper is > just lucky to trigger it. There shouldn't be anything oom_reaper > specific here. Maybe there is

Re: [PATCH 1/2] mm, oom: introduce oom reaper

On Thu 24-12-15 20:06:50, Tetsuo Handa wrote: > Michal Hocko wrote: > > This is VM_BUG_ON_PAGE(page_mapped(page), page), right? Could you attach > > the full kernel log? It all smells like a race when OOM reaper tears > > down the mapping and there is a truncate still in progress. But hitting > > t

Re: [PATCH 1/2] mm, oom: introduce oom reaper

On Thu 24-12-15 13:44:03, Ross Zwisler wrote: > On Thu, Dec 24, 2015 at 2:47 AM, Michal Hocko wrote: > > On Wed 23-12-15 16:00:09, Ross Zwisler wrote: > > [...] > >> While running xfstests on next-20151223 I hit a pair of kernel BUGs > >> that bisected to this commit: > >> > >> 1eb3a80d8239 ("mm,

ACPI-fan: Another source code review around null pointer handling?

Hello, I have looked at the source file for the ACPI fan driver once more. I would appreciate if a specific implementation detail can be clarified there. Static source code analysis can point out that functions like the following share an approach for error detection and corresponding exception h

平时最多也就联系了三千家，全球还有十几万客户在哪里？

您好: 您还在用ali平台开发外贸客户? 还在使用展会宣传企业和产品? 你out了!!! 当前外贸客户开发难，您是否也在寻找展会，B2B之外好的渠道？ 行业全球十几万客户，平时最多也就联系了三千家，您是否想把剩下的也开发到？ 加QQ1286754208给您演示下主动开发客户的方法，先用先受益，已经有近万家企业领先您使用！！。 广东省商业联合会推荐，主动开发客户第一品牌，近万家企业正在获益。您可以没有使用，但是不能没有了解。 -- To unsubscribe from this list: send the line "unsubsc

Re: [PATCH v2 0/2] Improve drm_of_component_probe() and move rockchip to use it

On Thu, 24 Dec 2015 12:36:10 + Russell King - ARM Linux wrote: > It seems that you're trying to work around a limitation in Linux by > modifying the hardware representation... Sorry to come back to this topic, but I think you are wrong. Looking at the imx6 DTs, the problem comes from the di

Re: crypto: algif_skcipher - Require setkey before accept(2)

On Fri, 25 Dec 2015, Herbert Xu wrote: > On Fri, Dec 25, 2015 at 07:54:48AM +0100, Julia Lawall wrote: > > Lines 766, 767 don't look correct at all. > > Thanks Julia. I have sent an updated patch in the original thread. > I wonder why I haven't received the original kbuild test robot > email t

Re: [PATCH 2/2] usb: gadget: f_midi: added spinlock on transmit function

On Tue, Dec 22, 2015 at 04:08:06PM +, Felipe F. Tonello wrote: > Since f_midi_transmit is called by both ALSA and USB frameworks, it can > potentially cause a race condition between both calls. This is bad because the > way f_midi_transmit is implemented can't handle concurrent calls. This is d