Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

Reviewed-by: Sagi Grimberg

Re: [PATCH 1/1] dmaengine:jz4740:fix memory leak

On 04/04/2018 05:21 AM, Xidong Wang wrote: > In function jz4740_dma_probe(), the memory allocated by > clk_get() is not released on the error path that ret, which holds > the return value of dma_async_device_register(), is not NULL. > This will result in a memory leak bug. > > Signed-off-by:

Re: [PATCH V3 4/4] genirq/affinity: irq vector spread among online CPUs as far as possible

On Wed, 4 Apr 2018, Thomas Gleixner wrote: > I'm aware how that hw-queue stuff works. But that only works if the > spreading algorithm makes the interrupts affine to offline/not-present CPUs > when the block device is initialized. > > In the example above: > > > > > irq 39, cpu list 0,4

[PATCH] [v2] rbd: avoid Wreturn-type warnings

A new set of warnings appeared in next-20180403 in some configurations when gcc cannot see that rbd_assert(0) leads to an unreachable code path: drivers/block/rbd.c: In function 'rbd_img_is_write': drivers/block/rbd.c:1397:1: error: control reaches end of non-void function [-Werror=return-type]

Re: [PATCH 3/4] gpio: Remove VLA from xra1403 driver

On Wed, Mar 28, 2018 at 7:27 PM, Laura Abbott wrote: > On 03/28/2018 12:27 AM, Geert Uytterhoeven wrote: >> >> Hi Laura, >> >> On Sat, Mar 10, 2018 at 1:10 AM, Laura Abbott wrote: >>> >>> The new challenge is to remove VLAs from the kernel >>> (see

Re: [PATCH v5 07/13] ARM: smp: Add initialization of CNTVOFF

Hi Mylène, On 03/04/18 07:18, Mylène Josserand wrote: > The CNTVOFF register from arch timer is uninitialized. > It should be done by the bootloader but it is currently not the case, > even for boot CPU because this SoC is booting in secure mode. > It leads to an random offset value meaning that

Re: [GIT PULL] Kernel lockdown for secure boot

On Wed, Apr 04, 2018 at 08:57:43AM -0400, Theodore Y. Ts'o wrote: > On Wed, Apr 04, 2018 at 04:30:18AM +, Matthew Garrett wrote: > > What I'm afraid of is this turning into a "security" feature that ends up > > being circumvented in most scenarios where it's currently deployed - eg, > > module

Re: [PATCH v3 2/4] mfd: add Gateworks System Controller core driver

> What about the 'reset' functionality? Is there something in the power > supply API for hooking in a GPIO based power switch (in my case it > would be i2c) as I would think that would be common for ATX supplies? > I didn't see anything in Documentation/power. > > This is what led me to the

Re: [PATCH v2] tools: fix cross-compile var clobbering

On 01/07/2018, 10:40 PM, Martin Kelly wrote: > From: Martin Kelly ... > --- a/tools/power/acpi/Makefile.config > +++ b/tools/power/acpi/Makefile.config > @@ -56,9 +56,6 @@ INSTALL_SCRIPT = ${INSTALL_PROGRAM} > # to compile vs uClibc, that can be done here as well. >

Re: [PATCH] sched: support dynamiQ cluster

On 4 April 2018 at 12:44, Valentin Schneider wrote: > Hi, > > On 03/04/18 13:17, Vincent Guittot wrote: >> Hi Valentin, >> > [...] >>> >>> I believe ASYM_PACKING behaves better here because the workload is only >>> sysbench threads. As stated above, since task

[no subject]

utente webmail Tieni presente che il 95% delle tue e-mail ricevute dopo lultima volta che hai bisogno di aggiornare il tuo server di versione webmail nel nostro database sono state ritardate. Per ricevere e inviare i tuoi messaggi su base regolare. Il nostro team tecnico di webmail aggiorner

Re: [PATCH] lib: logic_pio: Fix potential NULL pointer dereference

[+cc linux-pci] On Tue, Apr 03, 2018 at 04:15:05PM -0500, Gustavo A. R. Silva wrote: > new_range is being dereferenced before it is null checked, hence > there is a potential null pointer dereference. > > Fix this by moving the pointer dereference after new_range has > been properly null

Re: REGRESSION/TEST FAILURE caused by DEBUG_RWSEMS

On 04/04/2018 09:23 AM, Theodore Y. Ts'o wrote: > The commit 5149cbac4235: "locking/rwsem: Add DEBUG_RWSEMS to look for > lock/unlock emismatches" (newly added in this merge window) will cause > xfstests tests failures in generic/068 for all file systems. > > This is because the freeze and thaw

Re: [PATCH] dm: fix DAX dependency

On Wed, Apr 4, 2018 at 2:54 AM, Arnd Bergmann wrote: > Building device mapper with CONFIG_DAX=m now results in a link error: > > drivers/md/dm.o: In function `dm_put_table_device': > dm.c:(.text+0x33c): undefined reference to `put_dax' > drivers/md/dm.o: In function

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed 04-04-18 08:59:01, Steven Rostedt wrote: [...] > + /* > +* Check if the available memory is there first. > +* Note, si_mem_available() only gives us a rough estimate of > available > +* memory. It may not be accurate. But we don't care, we just want > +

[no subject]

пользователь веб-почты Обратите внимание, что 95% ваших писем, полученных после обновления сервера веб-почты в последнее время в нашей базе данных, были отложены. Регулярно получать и отправлять свои сообщения. Техническая команда нашей веб-почты обновит вашу учетную запись в течение 3

Re: [PATCH] x86: olpc: fix inconsistent MFD_CS5535 configuration

On Wed, Apr 4, 2018 at 4:09 PM, Thomas Gleixner wrote: > On Wed, 4 Apr 2018, Arnd Bergmann wrote: > >> This Kconfig warning appeared after a fix to the Kconfig validation. >> The GPIO_CS5535 driver depends on the MFD_CS5535 driver, but the former >> is selected in places where

Re: [PATCH v5 07/13] ARM: smp: Add initialization of CNTVOFF

On Wed, 04 Apr 2018 14:59:09 +0100, Mylène Josserand wrote: > > It'd be good to take this opportunity to refactor the shmobile code. > > I can do it in this series but I do not have any shmobile platforms so > I will not be able to test my modifications (only compilation). > > If someone can

[PATCH] [RFC][WIP] namespace.c: Allow some unprivileged proc mounts when not fully visible

Since Linux v4.2 with commit 1b852bceb0d1 ("mnt: Refactor the logic for mounting sysfs and proc in a user namespace"), new mounts of proc or sysfs in non init userns are only allowed when there is at least one fully-visible proc or sysfs mount. This is to enforce that proc/sysfs files masked by a

Re: [RESEND PATCH] ARM: pxa: stargate2: use device properties for at24 eeprom

On 4 April 2018 12:47:06 BST, Bartosz Golaszewski wrote: >We want to work towards phasing out the at24_platform_data structure. >There are few users and its contents can be represented using generic >device properties. Using device properties only will allow us to >significantly

Re: [RFC] drm/atomic+msm: add helper to implement legacy dirtyfb

On Wed, Apr 04, 2018 at 07:35:58AM -0400, Rob Clark wrote: > On Wed, Apr 4, 2018 at 6:21 AM, Daniel Vetter wrote: > > On Wed, Apr 04, 2018 at 12:03:00PM +0200, Daniel Vetter wrote: > >> On Tue, Apr 03, 2018 at 06:42:23PM -0400, Rob Clark wrote: > >> > Add an atomic helper to

Re: WARNING in account_page_dirtied

Hi, On Wed 04-04-18 10:24:48, Steven Whitehouse wrote: > On 03/04/18 13:05, Jan Kara wrote: > > Hello, > > > > On Sun 01-04-18 10:01:02, syzbot wrote: > > > syzbot hit the following crash on upstream commit > > > 10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00 2018 +) > > >

Re: [PATCH] nvme-multipath: implement active-active round-robin path selector

For PCIe devices the right policy is not a round robin but to use the pcie device closer to the node. I did a prototype for that long ago and the concept can work. Can you look into that and also make that policy used automatically for PCIe devices? I think that active/active makes sense

Re: [PATCH 2/4] nvmet-rdma: Use new SGL alloc/free helper for requests

@@ -565,24 +565,24 @@ static u16 nvmet_rdma_map_sgl_keyed(struct nvmet_rdma_rsp *rsp, { struct rdma_cm_id *cm_id = rsp->queue->cm_id; u64 addr = le64_to_cpu(sgl->addr); - u32 len = get_unaligned_le24(sgl->length); u32 key = get_unaligned_le32(sgl->key);

[PATCH 7/9] mtd: nand: qcom: check for operation errors in case of raw read

Currently there is no error checking for raw read. For raw reads, there won’t be any ECC failure but the operational failures are possible so schedule the NAND_FLASH_STATUS read after each codeword. Signed-off-by: Abhishek Sahu --- drivers/mtd/nand/qcom_nandc.c | 56

[PATCH 1/9] mtd: nand: qcom: use the ecc strength from device parameter

Currently the driver uses the ECC strength specified in device tree. The ONFI or JEDEC device parameter page contains the ‘ECC correctability’ field which indicates the number of bits that the host should be able to correct per 512 bytes of data. The ecc correctability is assigned in chip

Re: [PATCH v3 2/4] bus: fsl-mc: add restool userspace support

> I hear you. It is more complicated this way...having all these individual > objects vs just a single "bundle" of them that represents a NIC. But, that's > the way the DPAA2 hardware is, and we're implementing kernel support for > the hardware as it is. Hi Stuart I see we are not making any

[PATCH 5/9] mtd: nand: qcom: parse read errors for read oob also

read_page and read_oob both calls the read_page_ecc function. The QCOM NAND controller protect the OOB available bytes with ECC so read errors should be checked for read_oob also. Now this patch moves the error checking code inside read_page_ecc so caller does not have to check explicitly for read

[PATCH 2/9] mtd: nand: qcom: wait for desc completion in all BAM channels

The BAM has 3 channels - tx, rx and command. command channel is used for register read/writes, tx channel for data writes and rx channel for data reads. Currently, the driver assumes the transfer completion once it gets all the command descriptor completed. Sometimes, there is race condition in

[PATCH 8/9] mtd: nand: qcom: helper function for raw read

This patch does minor code reorganization for raw reads. Currently the raw read is required for complete page but for subsequent patches related with erased codeword bit flips detection, only few CW should be read. So, this patch adds helper function and introduces the read CW bitmask which

[PATCH 9/9] mtd: nand: qcom: erased page bitflips detection

Some of the newer nand parts can have bit flips in an erased page due to the process technology used. In this case, qpic nand controller is not able to identify that page as an erased page. Currently the driver calls nand_check_erased_ecc_chunk for identifying the erased pages but this won’t work

[PATCH 4/9] mtd: nand: qcom: fix null pointer access for erased buffer detection

parse_read_errors can be called with only oob buf also in which case data_buf will be NULL. If data_buf is NULL, then don’t treat this page as completely erased in case of ECC uncorrectable error. Signed-off-by: Abhishek Sahu --- drivers/mtd/nand/qcom_nandc.c | 7 +--

[PATCH 6/9] mtd: nand: qcom: support for checking read errors for last codeword

Add boolean function argument in parse_read_errors to identify whether the read error has been called for complete page read or only last codeword read. This will help in subsequent patches to detect ECC errors in case of last codeword read. Signed-off-by: Abhishek Sahu

[PATCH 3/9] mtd: nand: qcom: erased page detection for uncorrectable errors only

The NAND flash controller generates ECC uncorrectable error first in case of completely erased page. Currently driver applies the erased page detection logic for other operation errors also so fix this and return EIO for other operational errors. Signed-off-by: Abhishek Sahu

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed, 4 Apr 2018 08:20:39 +0200 Michal Hocko wrote: > > Now can you please explain to me why si_mem_available is not suitable > > for my purpose. > > Several problems. It is overly optimistic especially when we are close > to OOM. The available pagecache or slab

Re: [PATCH 3/4] tracing: Add action comparisons when testing matching hist triggers

On Wed, 4 Apr 2018 21:33:38 +0900 Masami Hiramatsu wrote: > Hmm, how can I undef ts0 and test it again? > If I can not clean it, the testcase must fail on the 2nd time. Tom, I already pulled in your patches and almost completed my tests (which obviously are not stress

Re: [PATCH 1/2] livepatch: Initialize shadow variables by init function safely

On Wed 2018-03-14 14:44:36, Josh Poimboeuf wrote: > On Wed, Mar 14, 2018 at 03:27:02PM -0400, Joe Lawrence wrote: > > On Tue, Mar 13, 2018 at 04:54:47PM +0100, Petr Mladek wrote: > > > The existing API allows to pass a sample data to initialize the shadow > > > data. It works well when the data

REGRESSION/TEST FAILURE caused by DEBUG_RWSEMS

The commit 5149cbac4235: "locking/rwsem: Add DEBUG_RWSEMS to look for lock/unlock emismatches" (newly added in this merge window) will cause xfstests tests failures in generic/068 for all file systems. This is because the freeze and thaw ioctls, by design, are run in different processes. It

Re: [PATCH 1/1] drm/i915:Do not use kfree() to free kmem_cache_alloc() return value

://github.com/0day-ci/linux/commits/Xidong-Wang/drm-i915-Do-not-use-kfree-to-free-kmem_cache_alloc-return-value/20180404-193341 base: git://anongit.freedesktop.org/drm-intel for-linux-next reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__

Re: [RFC] drm/atomic+msm: add helper to implement legacy dirtyfb

On Wed, Apr 4, 2018 at 8:16 AM, Daniel Vetter wrote: > On Wed, Apr 04, 2018 at 07:40:32AM -0400, Rob Clark wrote: >> On Wed, Apr 4, 2018 at 5:56 AM, Daniel Vetter wrote: >> > On Wed, Apr 04, 2018 at 11:10:08AM +0200, Thomas Hellstrom wrote: >> >> On 04/04/2018

[GIT PULL] /dev/random updates for 4.17

The following changes since commit 4a3928c6f8a53fa1aed28ccba227742486e8ddcb: Linux 4.16-rc3 (2018-02-25 18:50:41 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/random_for_linus for you to fetch changes up to

Re: [PATCH v5 2/2] KVM: X86: Add Force Emulation Prefix for "emulate the next instruction"

2018-04-04 19:59 GMT+08:00 David Hildenbrand : > >> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c >> index 1eb495e..a55ecef 100644 >> --- a/arch/x86/kvm/x86.c >> +++ b/arch/x86/kvm/x86.c >> @@ -146,6 +146,9 @@ bool __read_mostly enable_vmware_backdoor = false; >>

Re: [RFC][PATCH] tracing, printk: Force no hashing when trace_printk() is used

On Wed, 4 Apr 2018 09:49:27 +0200 Peter Zijlstra wrote: > On Tue, Apr 03, 2018 at 05:06:12PM -0400, Steven Rostedt wrote: > > If you are concerned about attack surface, I could make it a bit more > > difficult to tweak by malicious software. What about the patch below? > >

Re: dm: fix DAX dependency

On Wed, Apr 04 2018 at 5:54am -0400, Arnd Bergmann wrote: > Building device mapper with CONFIG_DAX=m now results in a link error: > > drivers/md/dm.o: In function `dm_put_table_device': > dm.c:(.text+0x33c): undefined reference to `put_dax' > drivers/md/dm.o: In function

Re: [PATCH v5 07/13] ARM: smp: Add initialization of CNTVOFF

Hi Marc, Thank you for the review. On Wed, 4 Apr 2018 14:01:48 +0100 Marc Zyngier wrote: > Hi Mylène, > > On 03/04/18 07:18, Mylène Josserand wrote: > > The CNTVOFF register from arch timer is uninitialized. > > It should be done by the bootloader but it is currently not

Re: [PATCH] x86: olpc: fix inconsistent MFD_CS5535 configuration

On Wed, 4 Apr 2018, Arnd Bergmann wrote: > This Kconfig warning appeared after a fix to the Kconfig validation. > The GPIO_CS5535 driver depends on the MFD_CS5535 driver, but the former > is selected in places where the latter is not: And why does GPIO_CS5535 not select MFD_CS5535 if it depends

Re: [PATCH] MAINTAINERS: add dri-devel for Android ION

On 04/04/2018 03:30 AM, Daniel Vetter wrote: Most of the other cross-driver gfx infrastructure (dma_buf, dma_fence) also gets cross posted to all the relevant gfx/memory lists. Doing the same for ION means people won't miss relevant patches. No problem from me, the rate of checkpatch fixups

Re: [PATCH 1/3] mm: memcontrol: Use cgroup_rstat for event accounting

On Wed, Apr 04, 2018 at 10:08:55AM -0400, Johannes Weiner wrote: > On Sat, Mar 24, 2018 at 09:08:59AM -0700, Tejun Heo wrote: > > @@ -91,6 +91,9 @@ struct mem_cgroup_stat_cpu { > > unsigned long events[MEMCG_NR_EVENTS]; > > unsigned long nr_page_events; > > unsigned long

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed, 4 Apr 2018 16:10:52 +0200 Michal Hocko wrote: > On Wed 04-04-18 08:59:01, Steven Rostedt wrote: > [...] > > + /* > > +* Check if the available memory is there first. > > +* Note, si_mem_available() only gives us a rough estimate of > > available

Re: [PATCH v2] MAINTAINERS: update entry for ARM/berlin

On Mon, Apr 2, 2018 at 4:28 AM, Jisheng Zhang wrote: > On Fri, 30 Mar 2018 15:59:32 +0200 Andrew Lunn wrote: > >> On Fri, Mar 30, 2018 at 11:02:11AM +0800, Jisheng Zhang wrote: >> > Synaptics has acquired the Multimedia Solutions Business of Marvell[1]. >> > So change

[PATCH] usb: select USB_COMMON for usb role switch config

The new axp288 extcon driver has no dependency on USB itself but calls the usb role switch helper functions. This causes a link error when USB_COMMON is disabled, as that subdirectory never gets entered: drivers/extcon/extcon-axp288.o: In function `axp288_usb_role_work':

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Tue, Apr 3, 2018 at 11:20 PM, Michal Hocko wrote: > On Tue 03-04-18 18:56:27, Steven Rostedt wrote: > [...] >> From your earlier email: >> >> > Except that it doesn't work. si_mem_available is not really suitable for >> > any allocation estimations. Its only purpose is to

Re: INFO: rcu detected stall in bitmap_parselist

Yury, are you OK with this patch? >From 7f21827cdfe9780b4949b22bcd19efa721b463d2 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Wed, 4 Apr 2018 21:12:10 +0900 Subject: [PATCH] lib/bitmap: Rewrite __bitmap_parselist(). syzbot is catching stalls at

Re: [PATCH] [mmc_block] Prevent bus reference leak in mmc_blk_init

On Thu, Mar 29, 2018 at 12:18 AM, Alexander Kappner wrote: > Upon module load, mmc_block allocates a bus with bus_register in > mmc_blk_init. This reference never gets freed during module unload. > Subsequent re-insertions of the module fail and BUG() is triggered: > > [

Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()

On Tue, Apr 03, 2018 at 10:43:14PM +0100, David Howells wrote: > Alan Stern wrote: > > > + * Returns: 1 if @lock is locked, 0 otherwise. > > + * However, on !CONFIG_SMP builds with !CONFIG_DEBUG_SPINLOCK, > > + * the return value is always 0 (see

Re: WARNING in account_page_dirtied

Hi, On 04/04/18 13:36, Jan Kara wrote: Hi, On Wed 04-04-18 10:24:48, Steven Whitehouse wrote: On 03/04/18 13:05, Jan Kara wrote: Hello, On Sun 01-04-18 10:01:02, syzbot wrote: syzbot hit the following crash on upstream commit 10b84daddbec72c6b440216a69de9a9605127f7a (Sat Mar 31 17:59:00

Re: [PATCH] [v2] rbd: avoid Wreturn-type warnings

On Wed, Apr 4, 2018 at 2:53 PM, Arnd Bergmann wrote: > A new set of warnings appeared in next-20180403 in some configurations > when gcc cannot see that rbd_assert(0) leads to an unreachable code > path: > > drivers/block/rbd.c: In function 'rbd_img_is_write': >

Re: [RFC] drm/atomic+msm: add helper to implement legacy dirtyfb

On Wed, Apr 4, 2018 at 8:26 AM, Daniel Vetter wrote: > On Wed, Apr 4, 2018 at 2:05 PM, Rob Clark wrote: >> On Wed, Apr 4, 2018 at 7:49 AM, Maarten Lankhorst >> wrote: >>> Op 04-04-18 om 13:37 schreef Rob Clark: On

Re: [PATCH v2 7/9] trace_uprobe/sdt: Fix multiple update of same reference counter

/commits/Ravi-Bangoria/trace_uprobe-Support-SDT-markers-having-reference-count-semaphore/20180404-201900 config: i386-randconfig-a0-201813 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors

Re: [PATCH v2] perf stat: enable 1ms interval for printing event counters values

Em Wed, Apr 04, 2018 at 09:05:16AM +0200, Jiri Olsa escreveu: > On Tue, Apr 03, 2018 at 09:18:33PM +0300, Alexey Budankov wrote: > > > > Currently print count interval for performance counters values is > > limited by 10ms so reading the values at frequencies higher than 100Hz > > is restricted

Re: [PATCH 1/1] drm/i915:Do not use kfree() to free kmem_cache_alloc() return value

-ci/linux/commits/Xidong-Wang/drm-i915-Do-not-use-kfree-to-free-kmem_cache_alloc-return-value/20180404-193341 base: git://anongit.freedesktop.org/drm-intel for-linux-next config: i386-randconfig-x009-201813 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save

[GIT PULL] ext4 updates for 4.17

The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2: Linux 4.16-rc1 (2018-02-11 15:04:29 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus for you to fetch changes up to

Re: [GIT PULL] Kernel lockdown for secure boot

On Wed, Apr 04, 2018 at 02:33:37PM +0100, David Howells wrote: > Theodore Y. Ts'o wrote: > > > Whoa. Why doesn't lockdown prevent kexec? Put another away, why > > isn't this a problem for people who are fearful that Linux could be > > used as part of a Windows boot virus in a

Are you in MAINTAINERS? Get your free Nitrokey Start.

TL,DR: If you are in MAINTAINERS (or have a @kernel.org email address), you can get a free Nitrokey Start to help secure your PGP private keys. https://kernel.org/nitrokey-digital-tokens-for-kernel-developers.html Hello, all: We've been promoting the use of PGP signatures with git repositories.

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed 04-04-18 10:11:49, Steven Rostedt wrote: > On Wed, 4 Apr 2018 08:23:40 +0200 > Michal Hocko wrote: > > > If you are afraid of that then you can have a look at > > {set,clear}_current_oom_origin() > > which will automatically select the current process as an oom victim

Re: [PATCH] phy: mapphone-mdm6600: add gpiolib dependency

Hi, On Wed, Apr 04, 2018 at 12:27:19PM +0200, Arnd Bergmann wrote: > Without gpiolib, the gpiod_get_array_value_cansleep() is an empty stub, > so gcc notices that the resulting array is never initialized: > > drivers/phy/motorola/phy-mapphone-mdm6600.c: In function 'phy_mdm6600_status': >

Re: [PATCH 3/8] bindings: PCI: designware: Add support for the EP in designware driver

Hi Lorenzo, On 04/04/2018 12:50, Lorenzo Pieralisi wrote: > On Wed, Mar 28, 2018 at 12:38:33PM +0100, Gustavo Pimentel wrote: > > Please always write a commit log even if it is trivial. Ok, Kishon has also refered that. On next patch version it'll contain a log description. > > Thanks, >

Re: [PATCH] [mmc_block] Prevent bus reference leak in mmc_blk_init

On 29 March 2018 at 11:52, Shawn Lin wrote: > On 2018/3/29 6:18, Alexander Kappner wrote: >> >> Upon module load, mmc_block allocates a bus with bus_register in >> mmc_blk_init. This reference never gets freed during module unload. >> Subsequent re-insertions of the

Re: [PATCH 0/3] mmc: meson-axg: initial support for AXG SoC platform

On 3 April 2018 at 12:06, Yixun Lan wrote: >The patches series try to enable basic eMMC support in the Meson-AXG > platfrom. > >Currently HS200 mode is tested with clock running at 166MHz, since > not all boards are stable to running 200MHz (due to tuning phase

Re: [PATCH v8 25/42] ARM: davinci: dm644x: add new clock init using common clock framework

On Wednesday 04 April 2018 12:17 PM, Sekhar Nori wrote: > On Tuesday 03 April 2018 10:00 PM, David Lechner wrote: >> On 04/03/2018 05:26 AM, Sekhar Nori wrote: >>> On Friday 16 March 2018 08:22 AM, David Lechner wrote: +static struct resource dm644x_pll1_resources[] = { +    { + 

[PATCH] x86: olpc: fix inconsistent MFD_CS5535 configuration

This Kconfig warning appeared after a fix to the Kconfig validation. The GPIO_CS5535 driver depends on the MFD_CS5535 driver, but the former is selected in places where the latter is not: WARNING: unmet direct dependencies detected for GPIO_CS5535 Depends on [m]: GPIOLIB [=y] && (X86 [=y] ||

Re: [PATCH] mmc: sdhci-cadence: send tune request twice to work around errata

On 4 April 2018 at 11:05, Masahiro Yamada wrote: > Hi. > > 2018-04-04 16:35 GMT+09:00 Ulf Hansson : >> On 27 March 2018 at 11:29, Masahiro Yamada >> wrote: >>> Cadence sent out an errata report to their

Re: [PATCH] mmc: card: Don't show eMMC RPMB and BOOT areas in /proc/partitions

On 27 February 2018 at 12:33, Harish Jenny K N wrote: > From: Andrew Gabbasov > > Since RPMB area is accessible via special ioctl only and boot areas > are unlikely to contain any partitions, exclude them all from listing > in

Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850

On Tue, Apr 3, 2018 at 3:13 PM, Andreas Radke wrote: > Am Mon, 2 Apr 2018 08:34:35 -0400 > schrieb Jason Andryuk : > >> The HP EliteBook G3 850 has a weird bug where a subsequent cold boot >> hangs while plugged in if Linux enables the Host Notify

[no subject]

Apply for a loan at 3% reply to this Email for more Info

Re: [PATCH] rbd: add missing return statements

On Wed, Apr 4, 2018 at 1:04 PM, Ilya Dryomov wrote: > On Wed, Apr 4, 2018 at 11:49 AM, Arnd Bergmann wrote: >> A new set of warnings appeared in next-20180403 in some configurations >> when gcc cannot see that rbd_assert(0) leads to an unreachable code >> path:

Re: [PATCH v2 7/9] trace_uprobe/sdt: Fix multiple update of same reference counter

/commits/Ravi-Bangoria/trace_uprobe-Support-SDT-markers-having-reference-count-semaphore/20180404-201900 config: x86_64-randconfig-x019-201813 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All

Re: [GIT PULL] Kernel lockdown for secure boot

On Wed, 2018-04-04 at 08:57 -0400, Theodore Y. Ts'o wrote: > On Wed, Apr 04, 2018 at 04:30:18AM +, Matthew Garrett wrote: > > What I'm afraid of is this turning into a "security" feature that ends up > > being circumvented in most scenarios where it's currently deployed - eg, > > module

Re: [PATCH v4] usb: dwc2: dwc2_vbus_supply_init: fix error check

Could this patch be picked up, please? Thanks, Tomeu On 26 March 2018 at 13:51, Heiko Stübner wrote: > Am Montag, 26. März 2018, 11:00:01 CEST schrieb Tomeu Vizoso: >> devm_regulator_get_optional returns -ENODEV if the regulator isn't >> there, so if that's the case we have to

Re: [PATCH] [net] nvmem: disallow modular CONFIG_NVMEM

For making things build again: Acked-by: Mike Looijmans I'd be interested in use-cases for having nvmem as a module, I cannot think of any. I am working on splitting of_get_nvmem_mac_address(), by moving most of its burden to the nvmem interface. Intend to create this "just give me my

Re: [GIT PULL] Kernel lockdown for secure boot

Theodore Y. Ts'o wrote: > Whoa. Why doesn't lockdown prevent kexec? Put another away, why > isn't this a problem for people who are fearful that Linux could be > used as part of a Windows boot virus in a Secure UEFI context? Lockdown mode restricts kexec to booting an

Re: [PATCH v5 01/13] ARM: move cputype definitions into another file

Hello Florian, On Tue, 3 Apr 2018 12:56:30 -0700 Florian Fainelli wrote: > On 04/02/2018 11:52 PM, Chen-Yu Tsai wrote: > > On Tue, Apr 3, 2018 at 2:18 PM, Mylène Josserand > > wrote: > >> To add the support for SMP on sun8i-a83t, we will

Re: [GIT PULL] Kernel lockdown for secure boot

Theodore Y. Ts'o wrote: > > Lockdown mode restricts kexec to booting an authorised image (where the > > authorisation may be by signature or by IMA). > > If that's true, then Matthew's assertion that lockdown w/o secure boot > is insecure goes away, no? No. Lockdown prevents

Re: [PATCH v30 2/4] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT

On Wed, Apr 04, 2018 at 10:07:51AM +0800, Wei Wang wrote: > On 04/04/2018 02:47 AM, Michael S. Tsirkin wrote: > > On Wed, Apr 04, 2018 at 12:10:03AM +0800, Wei Wang wrote: > > > +static int add_one_sg(struct virtqueue *vq, unsigned long pfn, uint32_t > > > len) > > > +{ > > > + struct scatterlist

Re: [PATCH 1/3] mm: memcontrol: Use cgroup_rstat for event accounting

On Sat, Mar 24, 2018 at 09:08:59AM -0700, Tejun Heo wrote: > @@ -91,6 +91,9 @@ struct mem_cgroup_stat_cpu { > unsigned long events[MEMCG_NR_EVENTS]; > unsigned long nr_page_events; > unsigned long targets[MEM_CGROUP_NTARGETS]; > + > + /* for cgroup rstat delta calculation */

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed, 4 Apr 2018 16:23:29 +0200 Michal Hocko wrote: > On Wed 04-04-18 10:11:49, Steven Rostedt wrote: > > On Wed, 4 Apr 2018 08:23:40 +0200 > > Michal Hocko wrote: > > > > > If you are afraid of that then you can have a look at > > >

Re: [PATCH] x86: olpc: fix inconsistent MFD_CS5535 configuration

On Wed, 4 Apr 2018, Arnd Bergmann wrote: > On Wed, Apr 4, 2018 at 4:09 PM, Thomas Gleixner wrote: > > On Wed, 4 Apr 2018, Arnd Bergmann wrote: > > > >> This Kconfig warning appeared after a fix to the Kconfig validation. > >> The GPIO_CS5535 driver depends on the MFD_CS5535

[PATCH] locking/rwsem: Add up_write_non_owner() for percpu_up_write()

The commit 8c5db92a705d ("locking/rwsem: Add DEBUG_RWSEMS to look for lock/unlock mismatches") causes a warning in ext4 fstests due to the fact that the freeze and thaw ioctls, by design, are run in different processes. This is not a bug in the commit itself. Rather, we need a up_write() variant

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed 04-04-18 10:25:27, Steven Rostedt wrote: > On Wed, 4 Apr 2018 16:10:52 +0200 > Michal Hocko wrote: > > > On Wed 04-04-18 08:59:01, Steven Rostedt wrote: > > [...] > > > + /* > > > +* Check if the available memory is there first. > > > +* Note,

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed 04-04-18 10:31:11, Steven Rostedt wrote: > On Wed, 4 Apr 2018 16:23:29 +0200 > Michal Hocko wrote: > > > On Wed 04-04-18 10:11:49, Steven Rostedt wrote: > > > On Wed, 4 Apr 2018 08:23:40 +0200 > > > Michal Hocko wrote: > > > > > > > If you are

Re: [PATCH v6 04/16] arc: Switch to generic free_initrd_mem.

Hi Shea, On Sun, 2018-04-01 at 10:59 -0400, Shea Levy wrote: > The first patch in this series added a weakly-defined generic > implementation, which is functionally identical to the > architecture-specific one removed here. > > Series boot-tested on RISC-V (which now uses the generic >

Crypto Update for 4.17

Hi Linus: Here is the crypto update for 4.17: API: - Add AEAD support to crypto engine. - Allow batch registration in simd. Algorithms: - Add CFB mode. - Add speck block cipher. - Add sm4 block cipher. - Add new test case for crct10dif. - Improve scheduling latency on ARM. - Add

Re: [PATCH] sched/rt: Fix rq->clock_update_flags < RQCF_ACT_SKIP warning

On Mon, Apr 02, 2018 at 09:49:54AM -0700, Davidlohr Bueso wrote: > While running rt-tests' pi_stress program I got the following splat: > > 444.884597] [ cut here ] > [ 444.894784] rq->clock_update_flags < RQCF_ACT_SKIP > [ 444.894798] WARNING: CPU: 27 PID: 0 at

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Wed 04-04-18 11:04:42, Steven Rostedt wrote: [...] > I'm not looking for perfect. In fact, I love what si_mem_available() > gives me now! Sure, it can say "there's enough memory" even if I can't > use it. Because most of the OOM allocations that happen with increasing > the size of the ring

Patch "media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32" has been added to the 3.18-stable tree

This is a note to let you know that I've just added the patch titled media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32 to the 3.18-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the

Patch "media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32" has been added to the 3.18-stable tree

This is a note to let you know that I've just added the patch titled media: v4l2-compat-ioctl32.c: copy clip list in put_v4l2_window32 to the 3.18-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the

Patch "media: v4l2-compat-ioctl32.c: don't copy back the result for certain errors" has been added to the 3.18-stable tree

This is a note to let you know that I've just added the patch titled media: v4l2-compat-ioctl32.c: don't copy back the result for certain errors to the 3.18-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename

Re: [GIT PULL] Kernel lockdown for secure boot

David Howells writes: > Andy Lutomirski wrote: > >> As far as I can tell, what's really going on here is that there's a >> significant contingent here that wants to prevent Linux from >> chainloading something that isn't Linux. > > You have completely the

Re: [PATCH] net: hns3: fix length overflow when CONFIG_ARM64_64K_PAGES

From: Tan Xiaojun Date: Wed, 4 Apr 2018 17:40:48 +0800 > When enable the config item "CONFIG_ARM64_64K_PAGES", the size of PAGE_SIZE > is 65536(64K). But the type of length is u16, it will overflow. So change it > to u32. > > Signed-off-by: Tan Xiaojun

Re: [PATCH] locking/qrwlock: Give priority to readers with irqs disabled to prevent deadlock

On 04.04.2018 18:51, Kirill Tkhai wrote: > On 04.04.2018 18:35, Peter Zijlstra wrote: >> On Wed, Apr 04, 2018 at 06:24:39PM +0300, Kirill Tkhai wrote: >>> The following situation leads to deadlock: >>> >>> [task 1] [task 2] [task 3] >>>

<    1   2   3   4   5   6   7   8   9   10   >