Re: [PATCH] staging: android: ion: add buffer flag update ioctl

On 12/23/18 6:47 PM, Zengtao (B) wrote: Hi laura: -Original Message- From: Laura Abbott [mailto:labb...@redhat.com] Sent: Friday, December 21, 2018 4:50 AM To: Zengtao (B) ; sumit.sem...@linaro.org Cc: Greg Kroah-Hartman ; Arve Hjønnevåg ; Todd Kjos ; Martijn Coenen ; Joel Fernandes ; d

Re: [PATCH] r8169: Add support for new Realtek Ethernet

On 02.01.2019 07:45, Kai-Heng Feng wrote: > There are two new Realtek Ethernet devices which are re-branded r8168h. > Add the IDs to to support them. > > Signed-off-by: Kai-Heng Feng > --- > drivers/net/ethernet/realtek/r8169.c | 2 ++ > 1 file changed, 2 insertions(+) > Reviewed-by: Heiner Kal

[PATCH V2] i2c: tegra: Fix Maximum transfer size

Tegra194 supports maximum 64K Bytes transfer per packet. Tegra186 and prior supports maximum 4K Bytes transfer per packet. This patch fixes this payload difference between Tegra194 and prior tegra chipsets using seperate i2c_adapter_quirks. Signed-off-by: Sowjanya Komatineni --- drivers/i2c/bus

Re: [PATCH] staging: android: ion: move map_kernel to ion_dma_buf_kmap

On 12/24/18 12:19 AM, Qing Xia wrote: Now, as Google's user guide, if userspace need clean ION buffer's cache, they should call ioctl(fd, DMA_BUF_IOCTL_SYNC, sync). Then we found that ion_dma_buf_begin_cpu_access/ion_dma_buf_end_cpu_access will do ION buffer's map_kernel, it's not necessary. And

RE: [PATCH V1] i2c: tegra: Fix Maximum transfer size

Thanks Peter. >> Tegra194 supports maximum 64K Bytes transfer per packet. >> Tegra186 and prior supports maximum 4K Bytes transfer per packet. >> >> This patch fixes this payload difference between Tegra194 and prior >> tegra chipsets. >> >> Signed-off-by: Sowjanya Komatineni >> --- >> driver

[GIT PULL] Please pull NFS client updates for 4.21

Hi Linus, The following changes since commit abc13275771fac77e2d7b129c289522dacb644b6: SUNRPC: Remove xprt_connect_status() (2018-12-18 11:04:10 -0500) are available in the Git repository at: git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.21-1 for you to fetch changes u

Re: [PATCH V2] i2c: tegra: Fix Maximum transfer size

On Wed, Jan 02, 2019 at 02:35:19PM -0800, Sowjanya Komatineni wrote: > Tegra194 supports maximum 64K Bytes transfer per packet. Linux I2C doesn't support more than 64K of transfers as well... > + .max_read_len = 65535, > + .max_write_len = 65535, ... so you can simply drop these lines.

Respond for details

I can help you secure a private loan , should you be interested please respond for more details . Thanks Allen

Re: [PATCH 06/20] IB/ipoib: drop useless LIST_HEAD

On Sun, Dec 23, 2018 at 09:57:01AM +0100, Julia Lawall wrote: > Drop LIST_HEAD where the variable it declares is never used. > > Commit 31c02e215700 ("IPoIB: Avoid using stale last_send counter > when reaping AHs") removed the uses, but not the declaration. > > The semantic patch that fixes this

Re: [alsa-devel] [PATCH v5 08/11] ASoC: Intel: atom: Make PCI dependency explicit

This is pointing to a kconfig issue on ia64 arch. arch/ia64/Kconfig:128:error: recursive dependency detected! arch/ia64/Kconfig:128:choice contains symbol IA64_HP_SIM arch/ia64/Kconfig:202:symbol IA64_HP_SIM is part of choice PM IA64_HP_SIM is both a choice and is selected. I did al

[GIT PULL] UML changes for 4.21

Linus, The following changes since commit 8fe28cb58bcb235034b64cbbb7550a8a43fd88be: Linux 4.20 (2018-12-23 15:55:59 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-4.21-rc1 for you to fetch changes up to 940b241d9050fc354f68

Re: [alsa-devel] [PATCH v5 08/11] ASoC: Intel: atom: Make PCI dependency explicit

On Wed, Jan 2, 2019 at 10:50 PM Pierre-Louis Bossart wrote: > > > > This is pointing to a kconfig issue on ia64 arch. > > > > arch/ia64/Kconfig:128:error: recursive dependency detected! > > arch/ia64/Kconfig:128:choice contains symbol IA64_HP_SIM > > arch/ia64/Kconfig:202:symbol IA64_HP_S

Re: [v4 PATCH 1/2] mm: swap: check if swap backing device is congested or not

On Sun, Dec 30, 2018 at 12:49:34PM +0800, Yang Shi wrote: > The test on my virtual machine with congested HDD shows long tail > latency is reduced significantly. > > Without the patch > page_fault1_thr-1490 [023] 129.311706: funcgraph_entry: #57377.796 > us | do_swap_page(); > page_fau

Re: [PATCH V1] i2c: tegra: Fix Maximum transfer size

On 2019-01-02 23:39, Sowjanya Komatineni wrote: >>> +static const struct i2c_adapter_quirks tegra194_i2c_quirks = { >>> + .flags = I2C_AQ_NO_ZERO_LEN, >> >> This is not mentioned in the commit message and the flag is not present in >> the old struct tegra_i2c_quirks above. Are you trying to snea

Re: [PATCH RFC 0/4] barriers using data dependency

On Wed, Jan 02, 2019 at 04:36:40PM -0500, Alan Stern wrote: > On Wed, 2 Jan 2019, Michael S. Tsirkin wrote: > > > So as explained in Documentation/memory-barriers.txt e.g. > > a load followed by a store require a full memory barrier, > > to avoid store being ordered before the load. > > Similarly

Re: [PATCH] infiniband: bnxt_re: qplib: Check the return value of send_message

On Wed, Dec 26, 2018 at 12:56:22PM -0600, Aditya Pakki wrote: > In bnxt_qplib_map_tc2cos(), bnxt_qplib_rcfw_send_message() can return > an error value. The fix returns the error from the latter function > upstream. > > Signed-off-by: Aditya Pakki > Acked-By: Devesh Sharma > --- > drivers/infini

Please help!: Keyboard backlight not working on my NP900X5N laptop

Hi guys, Sorry but still walking with this bug under my arm. I can't find the right group to file the bug on bugzilla and also on freenode I cannot find the right group. Please help! Regards, Jan On 01-01-19 13:48, Jan Vlietland wrote: Hi all, Greg K-H suggested to mail you guys. I ins

Re: [PATCH v4 04/10] KVM/x86: intel_pmu_lbr_enable

On Wed, Dec 26, 2018 at 2:01 AM Wei Wang wrote: > > The lbr stack is architecturally specific, for example, SKX has 32 lbr > stack entries while HSW has 16 entries, so a HSW guest running on a SKX > machine may not get accurate perf results. Currently, we forbid the > guest lbr enabling when the g

Re: [PATCH] infiniband/qedr: Potential null ptr dereference of qp

On Mon, Dec 24, 2018 at 12:24:45PM -0600, Aditya Pakki wrote: > idr_find() may fail and return a NULL pointer. The fix checks the > return value of the function and returns an error in case of NULL. > > Signed-off-by: Aditya Pakki > Acked-by: Michal Kalderon > --- > drivers/infiniband/hw/qedr/q

RE: [PATCH V2] i2c: tegra: Fix Maximum transfer size

Thanks Wolfram. >> Tegra194 supports maximum 64K Bytes transfer per packet. > >Linux I2C doesn't support more than 64K of transfers as well... > >> +.max_read_len = 65535, >> +.max_write_len = 65535, > >... so you can simply drop these lines. Oh Yes right, msg len is u16. will fix it. Th

[PATCH V3] i2c: tegra: Fix Maximum transfer size

Tegra194 supports maximum 64K Bytes transfer per packet. Tegra186 and prior supports maximum 4K Bytes transfer per packet. This patch fixes this payload difference between Tegra194 and prior tegra chipsets using separate i2c_adapter_quirks. Signed-off-by: Sowjanya Komatineni --- drivers/i2c/bus

Re: [PATCH v4 05/10] KVM/x86: expose MSR_IA32_PERF_CAPABILITIES to the guest

On Wed, Dec 26, 2018 at 2:01 AM Wei Wang wrote: > > Bits [0, 5] of MSR_IA32_PERF_CAPABILITIES tell about the format of > the addresses stored in the LBR stack. Expose those bits to the guest > when the guest lbr feature is enabled. > > Signed-off-by: Wei Wang > Cc: Paolo Bonzini > Cc: Andi Kleen

Re: [alsa-devel] [PATCH v5 08/11] ASoC: Intel: atom: Make PCI dependency explicit

On 1/2/19 4:58 PM, Sinan Kaya wrote: On Wed, Jan 2, 2019 at 10:50 PM Pierre-Louis Bossart wrote: This is pointing to a kconfig issue on ia64 arch. arch/ia64/Kconfig:128:error: recursive dependency detected! arch/ia64/Kconfig:128:choice contains symbol IA64_HP_SIM arch/ia64/Kconfig:202

[patch] Fix up l1ft documentation was Re: Taking a break - time to look back

Hi! > The next round of speculation-related issues including the scary L1TF > hardware bug was a way more "pleasant" experience to work on. While for > obvious reasons the mitigation development happened behind closed doors in > a smaller group of people, we were at least able to collaborate in a

[PATCH v3 0/2] soc: qcom: rmtfs-mem: Support non-root rmtfs daemons

This series contains minor fixes needed to better support running an rmtfs daemon from an unprivileged process: - Enable uevents on the child character device by adding a struct class to the parent. I needed these so that I could change the ownership of /dev/qcom_rmtfs_mem1, and drove myself crazy

[PATCH v3 1/2] soc: qcom: rmtfs-mem: Add class to enable uevents

Currently the qcom_rmtfs_memN devices are entirely invisible to the udev world. Add a class to the rmtfs device so that uevents fire when the device is added. Signed-off-by: Evan Green Reviewed-by: Brian Norris Reviewed-by: Bjorn Andersson --- Changes in v3: - Removed spurious whitespace chang

[PATCH v3 2/2] soc: qcom: rmtfs-mem: Make sysfs attributes world-readable

In order to run an rmtfs daemon as an unprivileged user, that user would need access to the phys_addr and size sysfs attributes. Sharing these attributes with unprivileged users doesn't really leak anything sensitive, since if you have access to physical memory, the jig is up anyway. Make those at

Re: KASAN: use-after-free Read in posix_lock_inode

On Wed, Jan 02 2019, Jeff Layton wrote: > On Wed, 2019-01-02 at 02:31 -0800, syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:e1ef035d272e Merge tag 'armsoc-defconfig' of git://git.ker.. >> git tree: upstream >> console output: https://syzkaller.apps

[PATCH v2] Bluetooth: Fix locking in bt_accept_enqueue() for BH context

With commit e16337622016 ("Bluetooth: Handle bt_accept_enqueue() socket atomically") lock_sock[_nested]() is used to acquire the socket lock before manipulating the socket. lock_sock[_nested]() may block, which is problematic since bt_accept_enqueue() can be called in bottom half context (e.g. from

[PATCH] Initialise mmu_notifier_range correctly

One of the paths in follow_pte_pmd() initialised the mmu_notifier_range incorrectly. Signed-off-by: Matthew Wilcox Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2") Tested-by: Dave Chinner diff --git a/mm/memory.c b/mm/memory.c index 2dd2f9ab57f4.

Re: [PATCH] kallsyms: lower alignment on ARM

On Sun, Dec 30, 2018 at 9:37 PM Mathias Krause wrote: > > As mentioned in the info pages of gas, the '.align' pseudo op's > interpretation of the alignment value is architecture specific. > It might either be a byte value or taken to the power of two. > > On ARM it's actually the latter which lead

[PATCH] memcg: localize memcg_kmem_enabled() check

Move the memcg_kmem_enabled() checks into memcg kmem charge/uncharge functions, so, the users don't have to explicitly check that condition. This is purely code cleanup patch without any functional change. Only the order of checks in memcg_charge_slab() can potentially be changed but the functional

Re: jump_label: move 'asm goto' support test to Kconfig

On Wed, Jan 2, 2019 at 9:14 PM Sedat Dilek wrote: > > Hi, > > I was not aware that CONFIG_JUMP_LABEL Kconfig setting depends on the > support of asm-goto. > > Currently, I am doing experiments with clang-7 and a snapshot of > clang-8 on Linux/x86. > These compilers have no asm-goto support. > > Wh

Re: [PATCH] nds32: remove redundant kernel-space generic-y

On Sun, Dec 16, 2018 at 11:49 PM Masahiro Yamada wrote: > > This commit removes redundant generic-y defines in > arch/nds32/include/asm/Kbuild. > > [1] It is redundant to define the same generic-y in both > arch/$(ARCH)/include/asm/Kbuild and > arch/$(ARCH)/include/uapi/asm/Kbuild. > >

Re: [PATCH] csky: remove meaningless header-y

On Mon, Dec 17, 2018 at 1:07 AM Masahiro Yamada wrote: > > Since commit fcc8487d477a ("uapi: export all headers under uapi > directories"), header-y is meaningless because headers under uapi > are all exported. > > Signed-off-by: Masahiro Yamada > --- Applied to linux-kbuild. > arch/csky/inc

Re: [LKP] bea5b158ff BUG: kernel reboot-without-warning in boot-around-mounting-root stage

On 01/02/2019 05:58 PM, Greg Kroah-Hartman wrote: On Wed, Jan 02, 2019 at 09:15:12AM +0800, kernel test robot wrote: Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit bea5b15

Re: INFO: task hung in generic_file_write_iter

On 2019/01/03 2:26, Jan Kara wrote: > On Thu 03-01-19 01:07:25, Tetsuo Handa wrote: >> On 2019/01/02 23:40, Jan Kara wrote: >>> I had a look into this and the only good explanation for this I have is >>> that sb->s_blocksize is different from (1 << >>> sb->s_bdev->bd_inode->i_blkbits). >>> If that

Re: [GIT PULL] Please pull NFS client updates for 4.21

On Wed, Jan 2, 2019 at 2:42 PM Schumaker, Anna wrote: > > We also were unable to track down a maintainer for Neil Brown's changes to > the generic cred code that are prerequisites to his RPC cred cleanup patches. > We've been asking around for several months without any response, so > hopefully it

[PATCH v2 1/7] sysfs/cpu: Add "Unknown" vulnerability state

There is a lot of variation in the Arm ecosystem. Because of this, there exist possible cases where the kernel cannot authoritatively determine if a machine is vulnerable. Rather than guess the vulnerability status in cases where the mitigation is disabled or the firmware isn't responding correctl

[PATCH v2 0/7] add system vulnerability sysfs entries

This series was originally by Mian Yousaf Kaukab. Arm64 machines should be displaying a human readable vulnerability status to speculative execution attacks in /sys/devices/system/cpu/vulnerabilities This series enables that behavior by providing the expected functions. Those functions expose th

[PATCH v2 4/7] arm64: add sysfs vulnerability show for spectre v1

From: Mian Yousaf Kaukab spectre v1, has been mitigated, and the mitigation is always active. Signed-off-by: Mian Yousaf Kaukab Signed-off-by: Jeremy Linton --- arch/arm64/kernel/cpu_errata.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/kernel/cpu_errata.c b/arch

[PATCH v2 7/7] arm64: enable generic CPU vulnerabilites support

From: Mian Yousaf Kaukab Enable CPU vulnerabilty show functions for spectre_v1, spectre_v2, meltdown and store-bypass. Signed-off-by: Mian Yousaf Kaukab Signed-off-by: Jeremy Linton --- arch/arm64/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kcon

[PATCH v2 6/7] arm64: add sysfs vulnerability show for speculative store bypass

From: Mian Yousaf Kaukab Return status based on ssbd_state and the arm64 SSBS feature. Return string "Unknown" in case CONFIG_ARM64_SSBD is disabled or arch workaround2 is not available in the firmware. Signed-off-by: Mian Yousaf Kaukab [Added SSBS logic] Signed-off-by: Jeremy Linton --- arch

[PATCH v2 5/7] arm64: add sysfs vulnerability show for spectre v2

Add code to track whether all the cores in the machine are vulnerable, and whether all the vulnerable cores have been mitigated. Once we have that information we can add the sysfs stub and provide an accurate view of what is known about the machine. Signed-off-by: Jeremy Linton --- arch/arm64/k

[PATCH v2 2/7] arm64: kpti: move check for non-vulnerable CPUs to a function

From: Mian Yousaf Kaukab Add is_meltdown_safe() which is a whitelist of known safe cores. Signed-off-by: Mian Yousaf Kaukab [Moved location of function] Signed-off-by: Jeremy Linton --- arch/arm64/kernel/cpufeature.c | 15 +++ 1 file changed, 11 insertions(+), 4 deletions(-) diff

[PATCH v2 3/7] arm64: add sysfs vulnerability show for meltdown

Add a simple state machine which will track whether all the online cores in a machine are vulnerable. Once that is done we have a fairly authoritative view of the machine vulnerability, which allows us to make a judgment about machine safety if it hasn't been mitigated. Signed-off-by: Jeremy Lint

Re: [PATCH] csky: remove meaningless header-y

On Thu, Jan 3, 2019 at 9:36 AM Masahiro Yamada wrote: > > On Mon, Dec 17, 2018 at 1:07 AM Masahiro Yamada > wrote: > > > > Since commit fcc8487d477a ("uapi: export all headers under uapi > > directories"), header-y is meaningless because headers under uapi > > are all exported. > > > > Signed-off

Re: [PATCH 2/2] m68k: generate uapi header and syscall table header files

Hi Firoz, Thank you for the patch! Yet something to improve: [auto build test ERROR on m68k/for-next] [also build test ERROR on next-20190102] [cannot apply to v4.20] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

[git pull] Input updates for v4.21-rc0

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. A tiny pull request this merge window unfortunately, should get more material in for the next release. - new driver for Raspberry Pi's touchscre

[PATCH 3/5] kbuild: generate asm-generic wrappers if mandatory headers are missing

Some time ago, Sam pointed out a certain degree of overwrap between generic-y and mandatory-y. (https://lkml.org/lkml/2017/7/10/121) I tweaked the meaning of mandatory-y a little bit; now it defines the minimum set of ASM headers that all architectures must have. If arch does not have specific im

[PATCH 2/5] arch: remove stale comments "UAPI Header export list"

These comments are leftovers of commit fcc8487d477a ("uapi: export all headers under uapi directories"). Prior to that commit, exported headers must be explicitly added to header-y. Now, all headers under the uapi/ directories are exported. Signed-off-by: Masahiro Yamada --- Changes in v2: None

[PATCH 4/5] arch: remove redundant generic-y defines

Now that Kbuild automatically creates asm-generic wrappers for missing mandatory headers, it is redundant to list the same headers in generic-y and mandatory-y. Suggested-by: Sam Ravnborg Signed-off-by: Masahiro Yamada Acked-by: Sam Ravnborg --- Changes in v2: - update csky as well - resol

[PATCH 5/5] kbuild: warn redundant generic-y

The generic-y is redundant under the following condition: - arch has its own implementation - the same header is added to generated-y - the same header is added to mandatory-y If a redundant generic-y is found, the warning like follows is displayed: scripts/Makefile.asm-generic:20: redund

[PATCH 1/5] riscv: remove redundant kernel-space generic-y

This commit removes redundant generic-y defines in arch/riscv/include/asm/Kbuild. [1] It is redundant to define the same generic-y in both arch/$(ARCH)/include/asm/Kbuild and arch/$(ARCH)/include/uapi/asm/Kbuild. Remove the following generic-y: errno.h fcntl.h ioctl

Re: [PATCH 4/4] kbuild: make LINUX_VERSION_CODE in more readable

On Mon, Dec 31, 2018 at 5:25 PM Masahiro Yamada wrote: > > Makefile does not need to calculate LINUX_VERSION_CODE. > Let's leave it to the preprocessor. > > This commit changes include/generated/uapi/linux/version.h as follows: > > Before: > > #define LINUX_VERSION_CODE 267264 > #define KERNEL

[PATCH] kbuild: use assignment instead of define ... endef for filechk_* rules

You do not have to use define ... endef for filechk_* rules. For simple cases, the use of assignment looks cleaner, IMHO. I updated the usage for scripts/Kbuild.include in case somebody misunderstands the 'define ... endif' is the requirement. Signed-off-by: Masahiro Yamada --- Kbuild

Re: KASAN: use-after-free Read in posix_lock_inode

On Thu, 2019-01-03 at 11:04 +1100, NeilBrown wrote: > On Wed, Jan 02 2019, Jeff Layton wrote: > > > On Wed, 2019-01-02 at 02:31 -0800, syzbot wrote: > > > Hello, > > > > > > syzbot found the following crash on: > > > > > > HEAD commit:e1ef035d272e Merge tag 'armsoc-defconfig' of > > > git:/

Re: possible deadlock in __wake_up_common_lock

On 2019/01/03 3:19, Qian Cai wrote: > On 1/2/19 1:06 PM, Mel Gorman wrote: > >> While I recognise there is no test case available, how often does this >> trigger in syzbot as it would be nice to have some confirmation any >> patch is really fixing the problem. > > I think I did manage to trigger

Re: [PATCH v2] misc: mic: fix a DMA pool free failure

On Tue, 2018-12-04 at 09:16 -0600, Wenwen Wang wrote: > In _scif_prog_signal(), a DMA pool is allocated if the MIC Coprocessor is > not X100, i.e., the boolean variable 'x100' is false. This DMA pool will be > freed eventually through the callback function scif_prog_signal_cb() with > the parameter

[PATCH v2] kbuild: remove unnecessary in-subshell execution

The commands surrounded by ( ) are executed in a subshell, but in most cases, we do not need to spawn an extra subshell. Signed-off-by: Masahiro Yamada --- Changes in v2: - fix build error of CONFIG_MODVERSIONS scripts/Makefile.build | 4 ++-- scripts/Makefile.lib | 28 ++--

Re: [PATCH v9 1/2] dmaengine: 8250_mtk_dma: add MediaTek uart DMA support

On Wed, Jan 2, 2019 at 10:13 AM Long Cheng wrote: > > In DMA engine framework, add 8250 uart dma to support MediaTek uart. > If MediaTek uart enabled(SERIAL_8250_MT6577), and want to improve > the performance, can enable the function. > > Signed-off-by: Long Cheng > --- > drivers/dma/mediatek/82

linux-next: manual merge of the vhost tree with Linus' tree

Hi all, Today's linux-next merge of the vhost tree got a conflict in: drivers/virtio/virtio_ring.c between commit: 138fd2514863 ("virtio_ring: add _split suffix for split ring functions") and various other commits from Linus' tree and commit: 7f86a211fabe ("virtio: use dependent_ptr_mb"

[PATCH] kbuild: remove unnecessary stubs for archheader and archscripts

Make simply skips a missing rule when it is marked as .PHONY. Remove the dummy targets. Signed-off-by: Masahiro Yamada --- Makefile | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/Makefile b/Makefile index 62c9890..0f0f689 100644 --- a/Makefile +++ b/Makefile @@ -1159,1

Re: [RFC PATCH 3/7] soc: mediatek: add support for the performance state

On Wed, Jan 2, 2019 at 10:01 PM Henry Chen wrote: > > Support power domain performance state, add header file for scp event. > > Signed-off-by: Henry Chen > --- > drivers/soc/mediatek/mtk-scpsys.c | 60 > +++ > drivers/soc/mediatek/mtk-scpsys.h | 22 +

Re: [PATCH 1/2] mm: introduce put_user_page*(), placeholder versions

On Wed, Dec 19, 2018 at 12:08:56PM +0100, Jan Kara wrote: > On Tue 18-12-18 21:07:24, Jerome Glisse wrote: > > On Tue, Dec 18, 2018 at 03:29:34PM -0800, John Hubbard wrote: > > > OK, so let's take another look at Jerome's _mapcount idea all by itself > > > (using > > > *only* the tracking pinned p

Re: [PATCH] Initialise mmu_notifier_range correctly

On Wed, Jan 02, 2019 at 04:21:26PM -0800, Matthew Wilcox wrote: > > One of the paths in follow_pte_pmd() initialised the mmu_notifier_range > incorrectly. > > Signed-off-by: Matthew Wilcox > Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for > invalidate_range_start/end calls v2") > Teste

[PATCH] memcg: schedule high reclaim for remote memcgs on high_work

If a memcg is over high limit, memory reclaim is scheduled to run on return-to-userland. However it is assumed that the memcg is the current process's memcg. With remote memcg charging for kmem or swapping in a page charged to remote memcg, current process can trigger reclaim on remote memcg. So, s

Re: KASAN: use-after-free Read in posix_lock_inode

On Wed, Jan 02 2019, Jeff Layton wrote: > On Thu, 2019-01-03 at 11:04 +1100, NeilBrown wrote: >> On Wed, Jan 02 2019, Jeff Layton wrote: >> >> > On Wed, 2019-01-02 at 02:31 -0800, syzbot wrote: >> > > Hello, >> > > >> > > syzbot found the following crash on: >> > > >> > > HEAD commit:e1ef03

Re: Keyboard backlight not working on my NP900X5N laptop

On Mon, Dec 31, 2018 at 08:40:43PM +0100, Jan Vlietland wrote: > Hi all, > Hey Jan, > Greg K-H suggested to mail you guys. > > I installed Linux 4.20.0-rc7 (downloaded, compiled and installed) on a > Samsung NP900X5N laptop and have noticed 3 bugs. 2 of them I found in > Bugzilla and replied

Re: [PATCH v9 1/2] dmaengine: 8250_mtk_dma: add MediaTek uart DMA support

Hi, While you are making changes, here are a few more: On 1/2/19 5:39 PM, Nicolas Boichat wrote: > diff --git a/drivers/dma/mediatek/Kconfig b/drivers/dma/mediatek/Kconfig > index 27bac0b..1a523c87 100644 > --- a/drivers/dma/mediatek/Kconfig > +++ b/drivers/dma/mediatek/Kconfig > @@ -1,4 +1,15 @

Re: [PATCH -next] IB/qib: Add missing err handle for qib_user_sdma_rb_insert

On 2019/1/3 3:07, Jason Gunthorpe wrote: > On Wed, Jan 02, 2019 at 08:40:50PM +0200, Leon Romanovsky wrote: >> On Wed, Jan 02, 2019 at 10:12:24AM -0700, Jason Gunthorpe wrote: >>> On Fri, Dec 21, 2018 at 10:19:38AM +0800, YueHaibing wrote: It should goto err handle if qib_user_sdma_rb_insert f

Re: [PATCH] x86/retpoline: change RETPOLINE into CONFIG_RETPOLINE

On 2019/1/3 1:23, Nadav Amit wrote: On Jan 1, 2019, at 5:17 PM, Zhenzhong Duan wrote: On 2019/1/1 7:42, Nadav Amit wrote: A recent enhancement intentionally fails the kernel build if the compiler does not support retpolines and CONFIG_RETPOLINE is set. However, the patch that introduced it

Re: Please help!: Keyboard backlight not working on my NP900X5N laptop

On Thu, Jan 03, 2019 at 12:20:15AM +0100, Jan Vlietland wrote: > Hi guys, > > Sorry but still walking with this bug under my arm. > > I can't find the right group to file the bug on bugzilla and also on > freenode I cannot find the right group. > > Please help! Hi Jan, I responded to your orig

Re: [RFC PATCH 6/7] soc: mediatek: add MT8183 dvfsrc support

On Wed, Jan 2, 2019 at 10:01 PM Henry Chen wrote: > > Add dvfsrc driver for MT8183 > > Signed-off-by: Henry Chen > --- > drivers/soc/mediatek/Kconfig | 15 ++ > drivers/soc/mediatek/Makefile | 1 + > drivers/soc/mediatek/mtk-dvfsrc.c | 473 > ++ >

Re: [PATCH V2] thermal: Fix locking in cooling device sysfs update cur_state

On 11/27/2018 05:43 PM, Thara Gopinath wrote: > Sysfs interface to update cooling device cur_state does not > currently holding cooling device lock sometimes leading to > stale values in cur_state if getting updated simultanelously > from user space and thermal framework. Adding the proper locking

Re: Shaohua Li

On 1/3/19 1:13 AM, Jens Axboe wrote: Hi, I've got some very sad news to share with you - over Christmas, Shaohua Li passed away after battling cancer for most of last year. It is really a sad news and a big lost for the community consider Shaohua's great contribution! As you know, Shaohua

Re: [GIT PULL] Please pull NFS client updates for 4.21

The pull request you sent on Wed, 2 Jan 2019 22:42:32 +: > git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-4.21-1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/e6b92572808467f35fd159d47c45b650de29e722 Thank you! -- Deet-doot-dot, I am a bot. ht

Re: [GIT PULL] nfsd

The pull request you sent on Wed, 2 Jan 2019 15:43:07 -0500: > git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.21 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/e45428a436765fcd154d461a2739b5640916dc00 Thank you! -- Deet-doot-dot, I am a bot. https://korg.wiki.ke

Re: [PATCH v5 6/6] arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile

On Fri, 2018-12-28 at 16:11 -0600, Rob Herring wrote: > On Fri, Dec 28, 2018 at 04:09:41PM +0800, Erin Lo wrote: > > From: Ben Ho > > > > Add basic chip support for Mediatek 8183, include > > pinctrl file, uart node with correct uart clocks, pwrap device > > M4U, smi-common and smi-larbs. > > >

[PATCH] In function rt274_i2c_probe(), if the regmap_read fails. The variable "val" could leave uninitialized but used in if statement.

Signed-off-by: Yizhuo --- sound/soc/codecs/rt274.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sound/soc/codecs/rt274.c b/sound/soc/codecs/rt274.c index 8f92e5c4dd9d..940658cac063 100644 --- a/sound/soc/codecs/rt274.c +++ b/sound/soc/codecs/rt274.c @@ -1113,7 +1113,7

Re: [PATCH V2] thermal: Fix locking in cooling device sysfs update cur_state

On 三, 2019-01-02 at 21:29 -0500, Thara Gopinath wrote: > On 11/27/2018 05:43 PM, Thara Gopinath wrote: > > > > Sysfs interface to update cooling device cur_state does not > > currently holding cooling device lock sometimes leading to > > stale values in cur_state if getting updated simultanelously

[PATCH v2] driver: uio: fix possible memory leak in uio_open

v1->v2: rename the "err_infoopen" to "err_idev_info" Fixes: 57c5f4df0a5a ("uio: fix crash after the device is unregistered") Signed-off-by: liujian --- drivers/uio/uio.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c index 5c10fc7

Re: [GIT PULL] s390 patches for the 4.21 merge window

The pull request you sent on Wed, 2 Jan 2019 08:43:54 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-4.21-1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/04a17edeca524b71dbb5be41a7002d247fbf34c0 Thank you! -- Deet-doot-dot, I am a b

Re: [GIT PULL] UML changes for 4.21

The pull request you sent on Wed, 02 Jan 2019 23:52:26 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-4.21-rc1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/6aa293d8ff0939802a6c86cee6cd152c1b0a7a0d Thank you! -- Deet-doot-dot, I am a bo

Re: [GIT PULL] one more clk change for the merge window

The pull request you sent on Wed, 2 Jan 2019 09:53:42 -0800: > https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git > tags/clk-for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/0f2107daec8137e1ea8bcd6df1323ffe46a2e873 Thank you! -- Deet-doot-dot, I

Re: [git pull] Input updates for v4.21-rc0

The pull request you sent on Wed, 2 Jan 2019 17:06:36 -0800: > git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/645ff1e8e704c4f33ab1fcd3c87f95cb9b6d7144 Thank you! -- Deet-doot-dot, I am a bot. htt

Re: [GIT PULL] Device properties framework fixes for v4.21-rc1

The pull request you sent on Wed, 2 Jan 2019 11:33:42 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git > devprop-4.21-rc1-2 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/01766d27d265afe7e93a8aa033afae5635d5aba0 Thank you! -- Deet-doot-dot

Re: [PULL] virtio, vhost: features, fixes, cleanups

The pull request you sent on Wed, 2 Jan 2019 16:23:23 -0500: > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/d548e65904ae43b0637d200a2441fc94e0589c30 Thank you! -- Deet-doot-dot, I am a bot.

Re: [GIT PULL] Mailbox changes for v4.21

The pull request you sent on Tue, 1 Jan 2019 23:34:36 -0600: > git://git.linaro.org/landing-teams/working/fujitsu/integration.git > tags/mailbox-v4.21 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/35ddb06a467538434b4139fbf5c02a2ef073162a Thank you! -- Deet-doot-do

[PATCH -next] um: Remove duplicated include from vector_user.c

Remove duplicated include. Signed-off-by: YueHaibing --- arch/um/drivers/vector_user.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/um/drivers/vector_user.c b/arch/um/drivers/vector_user.c index d2c17dd..b3f7b3c 100644 --- a/arch/um/drivers/vector_user.c +++ b/arch/um/drivers/vecto

RE: [PATCH] net: tsn: add an netlink interface between kernel and application layer

Hi Vinicius, Thanks! As comments below. Br, Po Liu > -Original Message- > From: Vinicius Costa Gomes [mailto:vinicius.go...@intel.com] > Sent: 2019年1月3日 3:02 > To: Po Liu ; net...@vger.kernel.org; linux- > ker...@vger.kernel.org > Cc: da...@davemloft.net; haus...@cisco.com; nicolas.fe.

[PATCH v2] netfilter: account ebt_table_info to kmemcg

The [ip,ip6,arp]_tables use x_tables_info internally and the underlying memory is already accounted to kmemcg. Do the same for ebtables. The syzbot, by using setsockopt(EBT_SO_SET_ENTRIES), was able to OOM the whole system from a restricted memcg, a potential DoS. By accounting the ebt_table_info,

linux-next: Tree for Jan 3

Hi all, Please do not add any material destined for the next merge window to your linux-next included trees until after -rc1 has been released. News: there will be no linux-next release tomorrow. Changes since 20190102: The vfs tree still had its build failure for which I applied a patch. The

[PATCH] vti4: Fix a ipip packet processing bug in 'IPCOMP' virtual tunnel

Recently we run a network test over ipcomp virtual tunnel.We find that if a ipv4 packet needs fragment, then the peer can't receive it. We deep into the code and find that when packet need fragment the smaller fragment will be encapsulated by ipip not ipcomp. So when the ipip packet goes into xfrm

[PATCH v2 0/2] USB Storage quirk for SMI SM3350

SMI SM3350 UFS-USB bridge controller cannot handle REQUEST SENSE command with long sense (96-bytes) well, and will even trap the controller into a state that refuses to do read/write command. Currently Linux uncondintionally set US_FL_SANE_SENSE for devices claiming SPC3+, which makes simply add U

[PATCH v2 1/2] USB: storage: don't insert sane sense for SPC3+ when bad sense specified

Currently the code will set US_FL_SANE_SENSE flag unconditionally if device claims SPC3+, however we should allow US_FL_BAD_SENSE flag to prevent this behavior, because SMI SM3350 UFS-USB bridge controller, which claims SPC4, will show strange behavior with 96-byte sense (put the chip into a wrong

[PATCH v2 2/2] USB: storage: add quirk for SMI SM3350

The SMI SM3350 USB-UFS bridge controller cannot handle long sense request correctly and will make the chip refuse to do read/write when requested long sense. Add a bad sense quirk for it. Signed-off-by: Icenowy Zheng --- drivers/usb/storage/unusual_devs.h | 12 1 file changed, 12 i

Re: [PATCH 1/2] mm: introduce put_user_page*(), placeholder versions

On 1/2/19 5:55 PM, Jerome Glisse wrote: > On Wed, Dec 19, 2018 at 12:08:56PM +0100, Jan Kara wrote: >> On Tue 18-12-18 21:07:24, Jerome Glisse wrote: >>> On Tue, Dec 18, 2018 at 03:29:34PM -0800, John Hubbard wrote: OK, so let's take another look at Jerome's _mapcount idea all by itself

Re: possible deadlock in __wake_up_common_lock

On 1/2/19 8:28 PM, Tetsuo Handa wrote: > On 2019/01/03 3:19, Qian Cai wrote: >> On 1/2/19 1:06 PM, Mel Gorman wrote: >> >>> While I recognise there is no test case available, how often does this >>> trigger in syzbot as it would be nice to have some confirmation any >>> patch is really fixing the p

Re: [PATCH] fsi:fsi-sbefifo: Fix possible concurrency use-after-free bugs in sbefifo_user_release

On Wed, 2019-01-02 at 09:34 +, David Howells wrote: > Jia-Ju Bai wrote: > > > + mutex_lock(&user->file_lock); > > sbefifo_release_command(user); > > free_page((unsigned long)user->cmd_page); > > + mutex_unlock(&user->file_lock); > > It shouldn't be necessary to do the free_page()

<    1   2   3   4   5   6   >