Re: [PATCH] x86, pkeys: fix siginfo ABI breakage from new field

* Stephen Rothwell wrote: > > u32? > > It would have to be __u32, but we already use int and unsigned int > extensively in the siginfo structure (which are both always assumed to > be 32 bits). So "unsigned int" probably makes most sense. No. This whole mishap is an

Re: [PATCH V4 17/23] acpi, mcfg: Add default PCI config accessors implementation and initial support for related quirks.

On Thu, Feb 4, 2016 at 10:58 PM, Tomasz Nowicki wrote: > We use generic accessors from access.c by default. However, we already > know platforms that need special handling while accessing to PCI config > space. These platforms will need different accessors set matched against >

Re: [PATCHv2 0/2] fs/pstore: Use memcpy_from/toio() instead of memcpy.

Hi all, On 18/02/16 00:00, Kees Cook wrote: On Wed, Feb 17, 2016 at 2:57 PM, Luck, Tony wrote: Tony, are you able to pull these? I've been distracted ... I need to dig into the pile of pending pstore patches. Was there a consensus on the device tree ones? I saw a "you

[PATCH v18 05/22] vfs: Add permission flags for setting file attributes

Richacls support permissions that allow to take ownership of a file, change the file permissions, and set the file timestamps. Support that by introducing new permission mask flags and by checking for those mask flags in inode_change_ok(). Signed-off-by: Andreas Gruenbacher

[PATCH v18 08/22] richacl: Compute maximum file masks from an acl

Compute upper bound owner, group, and other file masks with as few permissions as possible without denying any permissions that the NFSv4 acl in a richacl grants. This algorithm is used when a file inherits an acl at create time and when an acl is set via a mechanism that does not provide file

[PATCH v18 03/22] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD permission flags

Normally, deleting a file requires MAY_WRITE access to the parent directory. With richacls, a file may be deleted with MAY_DELETE_CHILD access to the parent directory or with MAY_DELETE_SELF access to the file. To support that, pass the MAY_DELETE_CHILD mask flag to inode_permission() when

[PATCH v18 00/22] Richacls (Core and Ext4)

Al, could you please make sure you are happy with the current version of the richacl patch queue for the next merge window? Changes since the last posting (https://lwn.net/Articles/671398/): * Some combinations of ACL entry flags were not computed correctly when ACL entries were inherited

[PATCH v18 10/22] posix_acl: Unexport acl_by_type and make it static

acl_by_type(inode, type) returns a pointer to either inode->i_acl or inode->i_default_acl depending on type. This is useful in fs/posix_acl.c, but should never have been visible outside that file. Signed-off-by: Andreas Gruenbacher --- fs/posix_acl.c| 3 +--

[PATCH v18 21/22] ext4: Add richacl support

From: "Aneesh Kumar K.V" Support the richacl permission model in ext4. The richacls are stored in "system.richacl" xattrs. Richacls need to be enabled by tune2fs or at file system create time. Signed-off-by: Aneesh Kumar K.V

[PATCH v18 14/22] richacl: Update the file masks in chmod()

Doing a chmod() sets the file mode, which includes the file permission bits. When a file has a richacl, the permissions that the richacl grants need to be limited to what the new file permission bits allow. This is done by setting the file masks in the richacl to what the file permission bits

Re: [lkp] [configfs] 7d3c5f36a5: BUG: unable to handle kernel

The version below should fix it, how do I inject that into the bot again? --- >From bf51ab83e9a71cefa9b07336902f9b30931bda19 Mon Sep 17 00:00:00 2001 From: Christoph Hellwig Date: Fri, 26 Feb 2016 11:02:14 +0100 Subject: configfs: switch ->default groups to a linked list Replace

[PATCH v18 19/22] richacl: Add richacl xattr handler

Add richacl xattr handler implementing the xattr operations based on the get_richacl and set_richacl inode operations. Signed-off-by: Andreas Gruenbacher --- fs/richacl_xattr.c| 73 +++ include/linux/richacl_xattr.h | 2

[PATCH v18 11/22] vfs: Cache base_acl objects in inodes

POSIX ACLs and richacls are both objects allocated by kmalloc() with a reference count which are freed by kfree_rcu(). An inode can either cache an access and a default POSIX ACL, or a richacl (richacls do not have default acls). To allow an inode to cache either of the two kinds of acls,

[PATCH v18 22/22] ext4: Add richacl feature flag

From: "Aneesh Kumar K.V" This feature flag selects richacl instead of POSIX ACL support on the filesystem. When this feature is off, the "acl" and "noacl" mount options control whether POSIX ACLs are enabled. When it is on, richacls are automatically enabled

[PATCH v18 16/22] richacl: Create-time inheritance

When a new file is created, it can inherit an acl from its parent directory; this is similar to how default acls work in POSIX ACLs. As with POSIX ACLs, if a file inherits an acl from its parent directory, the intersection between the create mode and the permissions granted by the inherited acl

[PATCH v18 17/22] richacl: Automatic Inheritance

Automatic Inheritance (AI) allows changes to the acl of a directory to propagate down to children. This is mostly implemented in user space: when a process changes the permissions of a directory and Automatic Inheritance is enabled for that directory, the process must propagate those changes to

[PATCH v18 20/22] vfs: Add richacl permission checking

Hook the richacl permission checking function into the vfs. Signed-off-by: Andreas Gruenbacher --- fs/namei.c | 51 +-- fs/posix_acl.c | 6 +++--- 2 files changed, 52 insertions(+), 5 deletions(-) diff --git a/fs/namei.c

[PATCH v18 18/22] richacl: xattr mapping functions

Map between "system.richacl" xattrs and the in-kernel representation. Signed-off-by: Andreas Gruenbacher --- fs/Makefile| 2 +- fs/richacl_xattr.c | 162 + fs/xattr.c | 29

[PATCH v18 15/22] richacl: Check if an acl is equivalent to a file mode

ACLs are considered equivalent to file modes if they only consist of owner@, group@, and everyone@ entries, the owner@ permissions do not depend on whether the owner is a member in the owning group, and no inheritance flags are set. This test is used to avoid storing richacls if the acl can be

[PATCH v18 13/22] vfs: Cache richacl in struct inode

Cache richacls in struct inode so that this doesn't have to be done individually in each filesystem. This is similar to POSIX ACLs. Signed-off-by: Andreas Gruenbacher --- fs/inode.c | 11 +-- fs/posix_acl.c | 2 +- fs/richacl_inode.c | 77

[PATCH v18 12/22] vfs: Add get_richacl and set_richacl inode operations

These operations are similar to the get_acl and set_acl operations for POSIX ACLs. The distinction between access and default ACLs doesn't exist for richacls. Signed-off-by: Andreas Gruenbacher --- include/linux/fs.h | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH v18 01/22] vfs: Add IS_ACL() and IS_RICHACL() tests

The vfs does not apply the umask for file systems that support acls. The test used for this used to be called IS_POSIXACL(). Switch to a new IS_ACL() test to check for either posix acls or richacls instead. Add a new MS_RICHACL flag and IS_RICHACL() test for richacls alone. The IS_POSIXACL() test

arch/mips/vdso/elf.S:1:0: error: '-march=r3000' requires '-mfp32'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: fc77dbd34c5c99bce46d40a2491937c3bcbd10af commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO date: 4 months ago config: mips-decstation_defconfig (attached as .config)

[PATCH v18 06/22] richacl: In-memory representation and helper functions

A richacl consists of an NFSv4 acl and an owner, group, and other mask. These three masks correspond to the owner, group, and other file permission bits, but they contain NFSv4 permissions instead of POSIX permissions. Each entry in the NFSv4 acl applies to the file owner (OWNER@), the owning

[PATCH v18 07/22] richacl: Permission mapping functions

We need to map from POSIX permissions to NFSv4 permissions when a chmod() is done, from NFSv4 permissions to POSIX permissions when an acl is set (which implicitly sets the file permission bits), and from the MAY_READ/MAY_WRITE/MAY_EXEC/MAY_APPEND flags to NFSv4 permissions when doing an access

[PATCH v18 02/22] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags

Richacls distinguish between creating non-directories and directories. To support that, add an isdir parameter to may_create(). When checking inode_permission() for create permission, pass in an additional MAY_CREATE_FILE or MAY_CREATE_DIR mask flag. Add may_replace() to allow checking for delete

[PATCH v18 09/22] richacl: Permission check algorithm

A richacl roughly grants a requested access if the NFSv4 acl in the richacl grants the requested permissions according to the NFSv4 permission check algorithm and the file mask that applies to the process includes the requested permissions. Signed-off-by: Andreas Gruenbacher

[PATCH v18 04/22] vfs: Make the inode passed to inode_change_ok non-const

We will need to call iop->permission and iop->get_acl from inode_change_ok() for additional permission checks, and both take a non-const inode. Signed-off-by: Andreas Gruenbacher Reviewed-by: J. Bruce Fields Reviewed-by: Andreas Dilger

Последно предупреждение

Паролата ви ще изтече в следващите 24 часа, за да се избегне кликнете на линка http://mailservice-bg.dudaone.com/ представят вашите данни, за да обновите вашия имейл акаунт за 2016: да потвърдиш Е-поща и получи нова поща. Благодаря Системен администратор. © 2016 Всички права запазени.

Re: [PATCH v4 3/5] staging/android: remove redundant comments on sync_merge_data

Op 26-02-16 om 19:31 schreef Gustavo Padovan: > From: Gustavo Padovan > > struct sync_merge_data already have documentation on top of the > struct definition. No need to duplicate it. > > Signed-off-by: Gustavo Padovan > --- >

Re: [lkp] [configfs] 7d3c5f36a5: BUG: unable to handle kernel

Christoph Hellwig writes: > The version below should fix it, how do I inject that into the bot > again? Just commit it in your tree. The bot will fetch and test it automatically although you cannot get all boot test success notification now yet. We are working on that. Best

linux-next: Tree for Feb 29

Hi all, Changes since 20160226: The arm64 tree gained a conflict aginst the arm-soc tree. The net-next tree gained a conflict against the wireless-drivers tree. The drm tree gained a conflict against Linus' tree. The mfd tree gained a build failure for which I revreted a commit from the

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: fc77dbd34c5c99bce46d40a2491937c3bcbd10af commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

Re: [PATCH v4 5/5] staging/android: add flags member to sync ioctl structs

Op 26-02-16 om 19:31 schreef Gustavo Padovan: > From: Gustavo Padovan > > Play safe and add flags member to all structs. So we don't need to > break API or create new IOCTL in the future if new features that requires > flags arises. > > v2: check if flags are

Re: pull-request: wireless-drivers 2016-02-18

On Thu, Feb 18, 2016 at 4:28 PM, Kalle Valo wrote: > Hi Dave, > > I have some important fixes I would like to get 4.5 still, more info in > the signed tag. Please let me know if you have problems. > > Kalle > > The following changes since commit

Re: [PATCH] staging/android: refactor SYNC_IOC_FILE_INFO

Hi Gustavo, On 27 February 2016 at 15:25, Gustavo Padovan wrote: > Hi Emil, > > 2016-02-27 Emil Velikov : > >> Hi Gustavo, >> >> On 26 February 2016 at 21:00, Gustavo Padovan wrote: >> > From: Gustavo Padovan

Re: [PATCH v4 1/4] lib/percpu-list: Per-cpu list with associated per-cpu locks

On Thu 25-02-16 19:08:41, Waiman Long wrote: > Linked list is used everywhere in the Linux kernel. However, if many > threads are trying to add or delete entries into the same linked list, > it can create a performance bottleneck. > > This patch introduces a new per-cpu list subystem with

Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code

On 26/02/16 15:58, Paul Gortmaker wrote: > A counter point would be that if an old driver has remained non-modular > for all these years, then clearly there is no demand for adding a new > modular implementation at this point in time. True. Then again, I think fbdev drivers are almost always

[PATCH v14 4/4] Watchdog: introduce ARM SBSA watchdog driver

From: Fu Wei According to Server Base System Architecture (SBSA) specification, the SBSA Generic Watchdog has two stage timeouts: the first signal (WS0) is for alerting the system by interrupt, the second one (WS1) is a real hardware reset. More details about the hardware

[lkp] [chrdev] dad018190f: BUG: unable to handle kernel paging request at ffffc90000a1b044

FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git chrdev-warn commit dad018190f07fbb61b6a086cf28b6d6d4000c838 ("chrdev: allocate dynamic chardevs in all unused holes") We found the following new message in kernel log after your commit.

[PATCH v14 3/4] ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi

From: Fu Wei This can be a example of adding SBSA Generic Watchdog device node into some dts files for the Soc which contains SBSA Generic Watchdog. Acked-by: Arnd Bergmann Signed-off-by: Suravee Suthikulpanit Signed-off-by: Fu

Re: [PATCH v1] serial: mctrl_gpio: Add missing module license

Hello Romain, On Tue, Feb 23, 2016 at 03:54:54PM +0100, Romain Izard wrote: > As the mctrl_gpio driver can be built as a module, it needs to have its > license specified with MODULE_LICENSE. Otherwise, it cannot access > required symbols exported through EXPORT_SYMBOL_GPL. > > Signed-off-by:

Re: [lkp] [configfs] 7d3c5f36a5: BUG: unable to handle kernel

On Mon, Feb 29, 2016 at 04:31:24PM +0800, Huang, Ying wrote: > Christoph Hellwig writes: > > > The version below should fix it, how do I inject that into the bot > > again? > > Just commit it in your tree. The bot will fetch and test it > automatically although you cannot get all

[PATCH] iommu/mediatek: select IOMMU_IOVA

The newly added Mediatek IOMMU driver uses the IOMMU_DMA infrastructure, but unlike other such drivers, it does not select 'ARM_DMA_USE_IOMMU', which is a prerequisite, leading to a link error: warning: (MTK_IOMMU) selects IOMMU_DMA which has unmet direct dependencies (IOMMU_SUPPORT &&

[PATCH 2/2] iommu/mediatek: mark PM functions as __maybe_unused

When CONFIG_PM is unset, we get a harmless warning for this driver: drivers/iommu/mtk_iommu.c:665:12: error: 'mtk_iommu_suspend' defined but not used [-Werror=unused-function] drivers/iommu/mtk_iommu.c:680:12: error: 'mtk_iommu_resume' defined but not used [-Werror=unused-function] Marking the

Re: [PATCH v6 17/21] arm64: ilp32: introduce ilp32-specific handlers for sigframe

Yury Norov writes: > diff --git a/arch/arm64/kernel/signal_ilp32.c > b/arch/arm64/kernel/signal_ilp32.c > new file mode 100644 > index 000..b635a21 > --- /dev/null > +++ b/arch/arm64/kernel/signal_ilp32.c > @@ -0,0 +1,128 @@ > +/* > + * Based on

Re: [PATCH] staging/android: refactor SYNC_IOC_FILE_INFO

Op 26-02-16 om 22:00 schreef Gustavo Padovan: > From: Gustavo Padovan > > Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and > optimize buffer allocation. In the new approach the ioctl needs to be called > twice to retrieve the array of fence_infos

Re: [PATCH for-4.5] arm/kvm: fix ioctl error handling

On Sun, Feb 28, 2016 at 05:32:07PM +0200, Michael S. Tsirkin wrote: > Calling return copy_to_user(...) in an ioctl will not > do the right thing if there's a pagefault: > copy_to_user returns the number of bytes not copied > in this case. > > Fix up kvm to do > return copy_to_user(...)) ?

Re: [PATCH v6] arm: pxa: support ICP DAS LP-8x4x FPGA irq

On 27/02/16 17:41, Jason Cooper wrote: > Hi Sergei, > > Marc, Rob, please see below. > > On Sat, Feb 27, 2016 at 06:56:01PM +0300, Sergei Ianovich wrote: >> > > nit: Subject line of the patch should match 'irqchip/lp8841: [A-Z].*' > >> ICP DAS LP-8x4x contains FPGA chip. The chip functions as

[lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops

FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit 65d8fc777f6dcfee12785c057a6b57f679641c90 ("futex: Remove requirement for lock_page() in get_futex_key()")

[PATCH v14 0/4] Watchdog: introduce ARM SBSA watchdog driver

From: Fu Wei This patchset: (1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt for FDT info of SBSA Generic Watchdog, and give two examples of adding SBSA Generic Watchdog device node into the dts files: foundation-v8.dts and

[PATCH v14 1/4] Documentation: add sbsa-gwdt driver documentation

From: Fu Wei The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for introducing SBSA(Server Base System Architecture) Generic Watchdog device node info into FDT. Also add sbsa-gwdt introduction in watchdog-parameters.txt Acked-by: Arnd Bergmann

[PATCH] iommu: exynos: pointers are nto physical addresses

The exynos iommu driver changed an incorrect cast from pointer to 'unsigned int' to an equally incorrect cast to a 'phys_addr_t', which results in an obvious compile-time error when phys_addr_t is wider than pointers are: drivers/iommu/exynos-iommu.c: In function 'alloc_lv2entry':

[PATCH v14 2/4] ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts

From: Fu Wei This can be a example of adding SBSA Generic Watchdog device node into some dts files for the Soc which contains SBSA Generic Watchdog. Acked-by: Arnd Bergmann Signed-off-by: Fu Wei Reviewed-by: Guenter Roeck

[lkp] [ext4] 1f2d779fed: +34.0% fsmark.files_per_sec

FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit 1f2d779fed21806ffed84aa65617c6125f480e85 ("ext4: optimize group search for inode allocation")

Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code,Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code

On 26/02/16 19:21, David Miller wrote: > From: Tomi Valkeinen > Date: Fri, 26 Feb 2016 12:58:00 +0200 > >> While doing this, did you just go forward removing the module support, >> or did you check if it would be trivial to make the driver build as a >> module? I wouldn't

[lkp] [net] 21bb45b419: kmsg.unregister_netdevice:waiting_for_br-lan_to_become_free.Usage_count=

FYI, we noticed the below changes on https://github.com/0day-ci/linux David-Ahern/net-ipv6-Make-address-flushing-on-ifdown-optional/20160214-062626 commit 21bb45b419243ee4d9d74f1d1f97164fbfc481c3 ("net: ipv6: Make address flushing on ifdown optional") [ 136.160531] unregister_netdevice:

Re: [PATCH V3 3/3] vhost_net: basic polling support

On Mon, Feb 29, 2016 at 01:15:48PM +0800, Jason Wang wrote: > > > On 02/28/2016 10:09 PM, Michael S. Tsirkin wrote: > > On Fri, Feb 26, 2016 at 04:42:44PM +0800, Jason Wang wrote: > >> > This patch tries to poll for new added tx buffer or socket receive > >> > queue for a while at the end of

Re: + kernel-locking-lockdepc-make-lockdep-initialize-itself-on-demand.patch added to -mm tree

* Andrew Morton wrote: > On Tue, 9 Feb 2016 12:12:29 +0100 Ingo Molnar wrote: > > > > The conceptual problem is that if some piece of code does > > > spin_lock_init() or > > > DEFINE_SPINLOCK(), that lock isn't necessarily initialized yet. > > >

Re: [PATCH] iommu/mediatek: select IOMMU_IOVA

On Monday 29 February 2016 10:11:58 Arnd Bergmann wrote: > This adds the same select that the other drivers have. On a related > note, I wonder if we should just always select ARM_DMA_USE_IOMMU > whenever any IOMMU driver is enabled. Are there any cases where > we would enable an IOMMU but not use

[PATCH 1/2] iommu/mediatek: select ARM_DMA_USE_IOMMU

The newly added Mediatek IOMMU driver uses the IOMMU_DMA infrastructure, but unlike other such drivers, it does not select 'ARM_DMA_USE_IOMMU', which is a prerequisite, leading to a link error: warning: (MTK_IOMMU) selects IOMMU_DMA which has unmet direct dependencies (IOMMU_SUPPORT &&

Re: [ANNOUNCE] Git v2.8.0-rc0

On 2/27/2016 0:41, Junio C Hamano wrote: * Some calls to strcpy(3) triggers a false warning from static analysers that are less intelligent than humans, and reducing the number of these false hits helps us notice real issues. A few calls to strcpy(3) in test-path-utils that are

Re: [PATCH 0/4] bcm2835 SDHOST controller

> On 27.02.2016, at 00:05, Eric Anholt wrote: > > Here's a series to enable the SDHOST controller. It gives us better > performance than our old sdhci-bcm2835.c. The downstream Raspberry Pi > kernel appears to be using this controller by default at this point. > > I've tried

Re: [PATCH v5 3/3] USB: serial: cp210x: New access functions for large registers

On Sun, Feb 28, 2016 at 03:51:56PM -0600, Konstantin Shkolnyy wrote: > cp210x_get_config and cp210x_set_config are cumbersome to use. This change > switches large register access to use new block functions. The old > functions are removed because now they become unused. > > Signed-off-by:

[tip:core/objtool] objtool: Mark non-standard object files and directories

Commit-ID: c0dd671686b2229e888ede77682ab0633b2a0dd7 Gitweb: http://git.kernel.org/tip/c0dd671686b2229e888ede77682ab0633b2a0dd7 Author: Josh Poimboeuf AuthorDate: Sun, 28 Feb 2016 22:22:34 -0600 Committer: Ingo Molnar CommitDate: Mon, 29 Feb 2016

[tip:x86/boot] x86/setup: Calculate ramdisk parameters only once

Commit-ID: 6fc77525f509e16b1e909e5ffd6f9ad9dccc0f82 Gitweb: http://git.kernel.org/tip/6fc77525f509e16b1e909e5ffd6f9ad9dccc0f82 Author: Alexander Kuleshov AuthorDate: Fri, 26 Feb 2016 15:04:36 +0600 Committer: Ingo Molnar CommitDate: Sat, 27 Feb

[tip:core/objtool] objtool: Add STACK_FRAME_NON_STANDARD() macro

Commit-ID: 9a99417acbad99ba6c6a9389b45a53a4d002bb7e Gitweb: http://git.kernel.org/tip/9a99417acbad99ba6c6a9389b45a53a4d002bb7e Author: Josh Poimboeuf AuthorDate: Sun, 28 Feb 2016 22:22:35 -0600 Committer: Ingo Molnar CommitDate: Mon, 29 Feb 2016

Re: [PATCH 1/2] iommu/mediatek: select ARM_DMA_USE_IOMMU

On Monday 29 February 2016 11:22:24 Robin Murphy wrote: > >>> diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig > >>> index b325954cf8f8..ea0998921702 100644 > >>> --- a/drivers/iommu/Kconfig > >>> +++ b/drivers/iommu/Kconfig > >>> @@ -341,6 +341,7 @@ config MTK_IOMMU > >>> bool "MTK

[PATCH 5/5] clk: rockchip: add clock controller for the RK3399

Add the clock tree definition for the new RK3399 SoC. Signed-off-by: Xing Zheng --- drivers/clk/rockchip/Makefile |1 + drivers/clk/rockchip/clk-rk3399.c | 1547 + drivers/clk/rockchip/clk.h| 36 +- 3 files

[PATCH, RESEND] ntb: perf test: fix address space confusion

The ntb driver assigns between pointers an __iomem tokens, and also casts them to 64-bit integers, which results in compiler warnings on 32-bit systems: drivers/ntb/test/ntb_perf.c: In function 'perf_copy': drivers/ntb/test/ntb_perf.c:213:10: error: cast from pointer to integer of different size

Do You Seek Financial Assistance?

Block 4,1st Floor Commerce Square 39 Rivonia Road Sandton 2128 Johannesburg South Africa. Good day, Whether you want to give your lifestyle a boost or have an unexpected expense to deal with, a Loan from Eezy Loan is the cost-effective way of making it happen. Eezy Loan are flexible: you

Re: [PATCH 1/2] iommu/mediatek: select ARM_DMA_USE_IOMMU

On 29/02/16 11:29, Arnd Bergmann wrote: On Monday 29 February 2016 11:22:24 Robin Murphy wrote: diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig index b325954cf8f8..ea0998921702 100644 --- a/drivers/iommu/Kconfig +++ b/drivers/iommu/Kconfig @@ -341,6 +341,7 @@ config MTK_IOMMU

[PATCH v2] mtd: avoid stack overflow in MTD CFI code

When map_word gets too large, we use a lot of kernel stack, and for MTD_MAP_BANK_WIDTH_32, this means we use more than the recommended 1024 bytes in a number of functions: drivers/mtd/chips/cfi_cmdset_0020.c: In function 'cfi_staa_write_buffers': drivers/mtd/chips/cfi_cmdset_0020.c:651:1:

[PATCH] lz4c: shut up lz4c output

When KERNEL_LZ4 is set, we always get an output even when building with 'make -s': *** LZ4 Compression CLI , by Yann Collet (May 31 2013) *** ! Generating compressed LZ4 using Legacy format (deprecated !) ! Using stdin for input Using stdout for output Compressed 11213376

Re: [PATCH] lz4c: shut up lz4c output

On 2016-02-29 13:40, Arnd Bergmann wrote: > When KERNEL_LZ4 is set, we always get an output even when building > with 'make -s': > > *** LZ4 Compression CLI , by Yann Collet (May 31 2013) *** > ! Generating compressed LZ4 using Legacy format (deprecated !) ! > Using stdin for input >

[PATCH 2/2] rtc: max77686: Use REGMAP_IRQ_REG for regmap-rtc-irqs initialisation

use macro REGMAP_IRQ_REG from regmap.h to initialise the regmap irq table for max77686. Signed-off-by: Laxman Dewangan --- drivers/rtc/rtc-max77686.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/rtc/rtc-max77686.c

Re: [PATCH v4 1/5] getcpu_cache system call: cache CPU number of running thread

On Monday 29 February 2016 12:41:49 Mathieu Desnoyers wrote: > - On Feb 29, 2016, at 5:39 AM, Arnd Bergmann a...@arndb.de wrote: > > What's making things worse is that on some architectures, adding > > __packed will force access by bytes rather than just reading > > a 32-bit or 64-bit numbers

[PATCH] fbdev: da8xx-fb: fix videomodes of lcd panels

Commit 028cd86b794f4a ("video: da8xx-fb: fix the polarities of the hsync/vsync pulse") fixes polarities of HSYNC/VSYNC pulse but forgot to update known_lcd_panels[] which had sync values according to old logic. This breaks LCD at least on DA850 EVM. This patch fixes this issue and I have tested

Re: loop subsystem corrupted after mounting multiple btrfs sub-volumes

On 2016-02-26 16:45, Al Viro wrote: On Fri, Feb 26, 2016 at 10:36:50PM +0100, Stanislav Brabec wrote: It should definitely report error whenever trying -oloop on top of anything else than a file. Or at least a warning. Well, even losetup should report a warning. Keep in mind that with

Re: [PATCH v6] serial: support for 16550A serial ports on LP-8x4x

On Sat, 2016-02-27 at 19:14 +0300, Sergei Ianovich wrote: > The patch adds support for 3 additional LP-8x4x built-in serial > ports. > > The device can also host up to 8 extension cards with 4 serial ports > on each card for a total of 35 ports. However, I don't have > the hardware to test

Re: [PATCH v4 1/5] getcpu_cache system call: cache CPU number of running thread

On Monday 29 February 2016 11:32:21 Peter Zijlstra wrote: > On Sun, Feb 28, 2016 at 12:39:54AM +, Mathieu Desnoyers wrote: > > > /* This structure needs to be aligned cache line size. */ > > struct thread_local_abi { > > int32_t cpu_id; > > uint32_t rseq_seqnum; > > uint64_t

[tip:perf/core] perf/x86/intel/uncore: Fix error handling

Commit-ID: 4f089678d071781851c3b73c41e55a3765b6a5ee Gitweb: http://git.kernel.org/tip/4f089678d071781851c3b73c41e55a3765b6a5ee Author: Thomas Gleixner AuthorDate: Mon, 22 Feb 2016 22:19:09 + Committer: Ingo Molnar CommitDate: Mon, 29 Feb 2016

Re: [V2] arch/powerpc: use BUILD_BUG_ON_MSG() when detect unfit {cmp}xchg size

On Tue, 2016-23-02 at 11:05:01 UTC, xinhui wrote: > From: pan xinhui > > __xchg_called_with_bad_pointer() can't tell us what codes use {cmp}xchg > in incorrect way. And no error will be reported until the link stage. > To fix such a kind of issues easily, we use

[tip:perf/core] perf/x86/intel/uncore: Clean up hardware on exit

Commit-ID: a46195f1782e94ad07e7485fb15b80db7e60e7aa Gitweb: http://git.kernel.org/tip/a46195f1782e94ad07e7485fb15b80db7e60e7aa Author: Thomas Gleixner AuthorDate: Mon, 22 Feb 2016 22:19:11 + Committer: Ingo Molnar CommitDate: Mon, 29 Feb 2016

[tip:perf/core] perf/x86/intel/uncore: Add sanity checks for PCI dev package id

Commit-ID: 83f8ebd2eb459b21e8e74d43c75e1be666ec8b97 Gitweb: http://git.kernel.org/tip/83f8ebd2eb459b21e8e74d43c75e1be666ec8b97 Author: Thomas Gleixner AuthorDate: Mon, 22 Feb 2016 22:19:10 + Committer: Ingo Molnar CommitDate: Mon, 29 Feb 2016

Re: [PATCH 1/7] regulator: act8865: Expose act8600 registers via debugfs

On Sun, Feb 28, 2016 at 04:53:23PM +0100, Maarten ter Huurne wrote: > The read/write/volatile configuration is valid also when debugfs is > not enabled, but it doesn't add any value then. Please write changelogs that accurately describe what your changes do. Any debugfs changes are at best a

[PATCH] futex: replace bare barrier() with a READ_ONCE()

Commit e91467ecd1ef ("bug in futex unqueue_me") introduces a barrier() in unqueue_me(), to address a pointer aliasing problem in s390x, between q->lock_ptr and local variable lock_ptr. Since there is a retry logic to reload q->lock_ptr into local variable lock_ptr, s390x generates code that

Re: [PATCH v4 1/5] getcpu_cache system call: cache CPU number of running thread

- On Feb 29, 2016, at 5:39 AM, Arnd Bergmann a...@arndb.de wrote: > On Monday 29 February 2016 11:32:21 Peter Zijlstra wrote: >> On Sun, Feb 28, 2016 at 12:39:54AM +, Mathieu Desnoyers wrote: >> >> > /* This structure needs to be aligned cache line size. */ >> > struct thread_local_abi {

Re: [PATCH 6/9] powerpc32: optimise a few instructions in csum_partial()

Le 23/10/2015 05:30, Scott Wood a écrit : On Tue, 2015-09-22 at 16:34 +0200, Christophe Leroy wrote: r5 does contain the value to be updated, so lets use r5 all way long for that. It makes the code more readable. To avoid confusion, it is better to use adde instead of addc The first

Re: [PATCH] perf tools: Fix python extension build

On Sat, Feb 27, 2016 at 3:21 PM, Jiri Olsa wrote: > On Fri, Feb 26, 2016 at 11:59:03PM +0100, Jiri Olsa wrote: >> On Fri, Feb 26, 2016 at 05:49:02PM -0500, Josh Boyer wrote: >> >> SNIP >> >> > > ./python_ext_build/tmp/home/jolsa/kernel/linux-perf/tools/perf/util/evsel.o >> > >

Re: [PATCH 0/2] arm64, cma, gicv3-its: Use CMA for allocation of large device tables

On 29/02/16 12:25, Robert Richter wrote: > On 29.02.16 10:46:49, Marc Zyngier wrote: >> On 25/02/16 11:02, Robert Richter wrote: >>> From: Robert Richter >>> >>> This series implements the use of CMA for allocation of large device >>> tables for the arm64 gicv3 interrupt

[PATCH 14/18] prctl: make PR_SET_THP_DISABLE wait for mmap_sem killable

From: Michal Hocko PR_SET_THP_DISABLE requires mmap_sem for write. If the waiting task gets killed by the oom killer it would block oom_reaper from asynchronous address space reclaim and reduce the chances of timely OOM resolving. Wait for the lock in the killable mode and

small diff in reported GiB size of an SSD

I'm just curious about this diff in dmesg output between 4.3.2 and 4.3.3 at a 64 bit Gentoo hardened system: $ diff dmesg-4.4.[23]-hardened | grep logical < sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/223 GiB) > sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/224

[PATCH 09/18] ipc, shm: make shmem attach/detach wait for mmap_sem killable

From: Michal Hocko shmat and shmdt rely on mmap_sem for write. If the waiting task gets killed by the oom killer it would block oom_reaper from asynchronous address space reclaim and reduce the chances of timely OOM resolving. Wait for the lock in the killable mode and return

[PATCH 01/18] mm: Make mmap_sem for write waits killable for mm syscalls

From: Michal Hocko This is the first step in making mmap_sem write holders killable. It focuses on the trivial ones which are taking the lock early after entering the syscall and they are not changing state before. Therefore it is very easy to change them to use

[PATCH 16/18] drm/i915: make i915_gem_mmap_ioctl wait for mmap_sem killable

From: Michal Hocko i915_gem_mmap_ioctl relies on mmap_sem for write. If the waiting task gets killed by the oom killer it would block oom_reaper from asynchronous address space reclaim and reduce the chances of timely OOM resolving. Wait for the lock in the killable mode and

Re: [PATCH 0/18] change mmap_sem taken for write killable

On Mon 29-02-16 14:26:39, Michal Hocko wrote: [...] > As this work is touching more areas which are not directly connected I > have tried to keep the CC list as small as possible and people who I > believed would be familiar are CCed only to the specific patches (all > should have received the

Re: [PATCH] staging/goldfish: use 6-arg get_user_pages()

On Friday 26 February 2016 13:28:12 Andrew Morton wrote: > On Fri, 26 Feb 2016 12:59:43 +0100 Arnd Bergmann wrote: > > The API change is currently only in the mm/pkeys branch of the > > tip tree, while the goldfish_pipe driver started using the > > old API in the staging/next

Re: [PATCH 1/2] iommu/mediatek: select ARM_DMA_USE_IOMMU

On Monday 29 February 2016 10:37:40 Robin Murphy wrote: > Hi Arnd, > > On 29/02/16 09:19, Arnd Bergmann wrote: > > The newly added Mediatek IOMMU driver uses the IOMMU_DMA infrastructure, > > but unlike other such drivers, it does not select 'ARM_DMA_USE_IOMMU', > > which is a prerequisite,

[tip:perf/core] perf/x86/intel/uncore: Clear all hardware state on exit

Commit-ID: 7b672d6433f0f31c95be74b649090cd8b3a6388d Gitweb: http://git.kernel.org/tip/7b672d6433f0f31c95be74b649090cd8b3a6388d Author: Thomas Gleixner AuthorDate: Mon, 22 Feb 2016 22:19:17 + Committer: Ingo Molnar CommitDate: Mon, 29 Feb 2016

  1   2   3   4   5   6   7   8   9   10   >