Re: scatterwalk_map_and_copy incorrect optimization

Jason A. Donenfeld wrote: > Hah, looks like I missed [1] by a couple weeks. Looks like it's been > settled then. > > Is this a stable@ candidate? Not really since it shouldn't cause any problems unless the stack is vmalloced. Cheers, -- Email: Herbert Xu

Re: [RFC PATCH 15/23] arm: use kconfig fragments for ARCH_PXA defconfigs (part 1)

Bartlomiej Zolnierkiewicz writes: > Replace [lpd270,lubbock,mainstone,pxa255-idp]_defconfig-s with > a Makefile target using merge_config. > > The patch was verified with doing: > > $ make [lpd270,...]_defconfig > $ make savedefconfig > > and comparing resulting

Urgent Pls

Dear Sir/madam My name is Mrs. Lisa Miller I am 63 years old, I am a dying woman who have decided to donate what I have to you/churches/ motherless babies/less privileged/widows.I was diagnosed for cancer for about 2 years ago. I have been touched by God to donate from what I have inherited

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On Fri, Dec 09, 2016 at 10:41:58PM +0800, Baoquan He wrote: > X86 64 kernel takes KERNEL_IMAGE_SIZE as the kernel text mapping size, > and it's fixed as compiling time, changing from 512M to 1G as long as > CONFIG_RANDOMIZE_BASE is enabled, though people specify kernel option > "nokaslr"

[PATCH 1/5] net: ethernet: ti: cpsw: use same macros to get active slave

Use the same, more convenient macros, to get active slave. Signed-off-by: Ivan Khoronzhuk --- drivers/net/ethernet/ti/cpsw.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c index

[PATCH 5/5] net: ethernet: ti: cpsw: sync rates for channels in dual emac mode

The channels are common for both ndevs in dual emac mode. Hence, keep in sync their rates. Signed-off-by: Ivan Khoronzhuk --- drivers/net/ethernet/ti/cpsw.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On 12/10/16 at 11:31am, Borislav Petkov wrote: > On Fri, Dec 09, 2016 at 10:41:58PM +0800, Baoquan He wrote: > > X86 64 kernel takes KERNEL_IMAGE_SIZE as the kernel text mapping size, > > and it's fixed as compiling time, changing from 512M to 1G as long as > > CONFIG_RANDOMIZE_BASE is enabled,

[RFC 4/7] ARM: s3c64xx: Annotate external clock frequencies __ro_after_init

The xtal_f and xusbxti_f static variables are modified only through __init accessors (like s3c64xx_set_xtal_freq()). Later these variables are used only in read-only way so we can mark them __ro_after_init to increase code safeness. Signed-off-by: Krzysztof Kozlowski ---

[PATCH 2/7] ARM: EXYNOS: Annotate iomem and pm_data pointers __ro_after_init

The pointers to __iomem sysram and exynos_pm_data are set only during initcalls. Later the pointers itself are used only in read-only way so we can mark them __ro_after_init to increase code safeness. Signed-off-by: Krzysztof Kozlowski --- arch/arm/mach-exynos/exynos.c |

[PATCH 5/7] ARM: SAMSUNG: Constify array of wake irqs passed to samsung_sync_wakemask

The samsung_sync_wakemask() iterates over passed array of wake irqs but does not modify it. Signed-off-by: Krzysztof Kozlowski --- arch/arm/plat-samsung/include/plat/wakeup-mask.h | 2 +- arch/arm/plat-samsung/wakeup-mask.c | 2 +- 2 files changed, 2 insertions(+),

[PATCH 7/7] ARM: s3c64xx: Constify wake_irqs

samsung_sync_wakemask() accepts pointer to const data so wake_irqs can be made const to increase safeness. Signed-off-by: Krzysztof Kozlowski --- arch/arm/mach-s3c64xx/pm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/mach-s3c64xx/pm.c

[PATCH 6/7] ARM: s3c24xx: Constify wake_irqs

samsung_sync_wakemask() accepts pointer to const data so wake_irqs can be made const to increase safeness. Signed-off-by: Krzysztof Kozlowski --- arch/arm/mach-s3c24xx/pm-s3c2412.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/7] ARM: s3c24xx: Constify few integer tables

These arrays are not modified so they can be made const. Signed-off-by: Krzysztof Kozlowski --- arch/arm/mach-s3c24xx/bast-irq.c | 4 ++-- arch/arm/mach-s3c24xx/iotiming-s3c2410.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 2/2] USB: OHCI: pxa27x:fix code errors

On Sat, Dec 10, 2016 at 01:13:28AM +, csmanjuvi...@gmail.com wrote: > From: Manjunath Goudar > > This patch will fix the checkpatch.pl following errors: > > ERROR: space prohibited after that open parenthesis '(' > ERROR: space prohibited before that close

Re: [PATCH] ARM: add cmpxchg64 helper for ARMv7-M

Hi Arnd, On Sat, Dec 10, 2016 at 11:36:34AM +0100, Arnd Bergmann wrote: > A change to the netfilter code in net-next introduced the first caller of > cmpxchg64 that can get built on ARMv7-M, leading to an error from the > assembler that points out the lack of 64-bit atomics on this architecture:

Re: Remaining crypto API regressions with CONFIG_VMAP_STACK

On Sat, Dec 10, 2016 at 04:16:43PM +0800, Herbert Xu wrote: > Why did you drop me from the CC list when you were replying to > my email? > Sorry --- this thread is Cc'ed to the kernel-hardening mailing list (which was somewhat recently revived), and I replied to the email that reached me from

RE: [PATCH v6 1/2] sparc: fix a building error reported by kbuild

Regards, -Gonglei > -Original Message- > From: linux-crypto-ow...@vger.kernel.org > [mailto:linux-crypto-ow...@vger.kernel.org] On Behalf Of Sam Ravnborg > Sent: Saturday, December 10, 2016 5:59 AM > To: Gonglei (Arei) > Cc: linux-kernel@vger.kernel.org; qemu-de...@nongnu.org; >

Re: [PATCH v8 3/3] iio: adc: add support for Allwinner SoCs ADC

Hi, Just some minor comments. On Fri, Dec 09, 2016 at 11:22:36AM +0100, Quentin Schulz wrote: > + /* > + * Since the thermal sensor needs the IP to be in touchscreen mode and > + * there is no register to know if the IP has finished its transition > + * between the two modes,

Re: [PATCH] llist: Clarify comments about when locking is needed

- On Dec 10, 2016, at 5:13 AM, Joel Fernandes joe...@google.com wrote: > llist.h comments are a bit confusing about when locking is needed versus when > it isn't. Clarify these comments a bit more and be a bit more descriptive > about > why locking is needed for llist_del_first. Could

[PATCH] ARM: add cmpxchg64 helper for ARMv7-M

A change to the netfilter code in net-next introduced the first caller of cmpxchg64 that can get built on ARMv7-M, leading to an error from the assembler that points out the lack of 64-bit atomics on this architecture: /tmp/ccMe7djj.s: Assembler messages: /tmp/ccMe7djj.s:367: Error: selected

Re: Misalignment, MIPS, and ip_hdr(skb)->version

On 2016-12-07 19:54, Jason A. Donenfeld wrote: > On Wed, Dec 7, 2016 at 7:51 PM, David Miller wrote: >> It's so much better to analyze properly where the misalignment comes from >> and address it at the source, as we have for various cases that trip up >> Sparc too. > >

[PATCH 2/5] net: ethernet: ti: cpsw: don't start queue twice

No need to start queues after cpsw is started as it will be done while cpsw_adjust_link(), after phy connection. Signed-off-by: Ivan Khoronzhuk --- drivers/net/ethernet/ti/cpsw.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/net/ethernet/ti/cpsw.c

[PATCH 4/5] net: ethernet: ti: cpsw: re-split res only when speed is changed

Don't re-split res in the following cases: - speed of phys is not changed - speed of phys is changed and no rate limited channels - speed of phys is changed and all channels are rate limited - phy is unlinked while dev is open - phy is linked back but speed is not changed The maximum speed is sum

[PATCH 3/5] net: ethernet: ti: cpsw: combine budget and weight split and check

Re-split weight along with budget. It simplify code a little and update state after every rate change. Also it's necessarily to move arguments checks to this combined function. Replace maximum rate check for an interface on maximum possible rate. Signed-off-by: Ivan Khoronzhuk

[PATCH 1/5] net: ethernet: ti: cpsw: improve re-split policy

This patches add several simplifications and improvements to set maximum rate for channels taking in account switch and dual emac mode. Don't re-split res in the following cases: - speed of phys is not changed - speed of phys is changed and no rate limited channels - speed of phys is changed and

Re: [PATCH] driver core: flush async calls before testing driver removal

Hello Greg, On 12/10/2016 09:32 AM, Greg Kroah-Hartman wrote: > On Sat, Dec 10, 2016 at 02:15:19AM +0200, Vladimir Zapolskiy wrote: >> If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false >> positives are reported for ATA controller drivers, because ATA port >> probes are done

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On 12/10/16 at 01:33pm, Borislav Petkov wrote: > On Sat, Dec 10, 2016 at 08:27:57PM +0800, Baoquan He wrote: > > Whether CONFIG_RANDOMIZE_BASE is yes or not, with 'nokaslr' specified, > > Kernel text mapping size should be 512M, just the same as no kaslr code > > compiled in. > > "should be"

[PATCH] net: nicvf: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- .../net/ethernet/cavium/thunder/nicvf_ethtool.c| 56 +++- 1 files changed, 31 insertions(+), 25 deletions(-)

Re: scatterwalk_map_and_copy incorrect optimization

On Fri, Dec 09, 2016 at 02:18:01PM +0100, Jason A. Donenfeld wrote: > Hi Herbert, > > The scatterwalk_map_and_copy function copies ordinary buffers to and > from scatterlists. These buffers can, of course, be on the stack, and > this remains the most popular use of this function -- getting info >

[RFC PATCH] arm64: make WANT_HUGE_PMD_SHARE depends on HUGETLB_PAGE

From: zhong jiang when HUGETLB_PAGE is disable, WANT_HUGE_PMD_SHARE contains the fuctions should not be use. therefore, we add the dependency. Signed-off-by: zhong jiang --- arch/arm64/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH 4.8 00/45] 4.8.14-stable review

On Fri, Dec 09, 2016 at 11:24:22AM -0700, Shuah Khan wrote: > On 12/09/2016 09:20 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.14 release. > > There are 45 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.8 00/45] 4.8.14-stable review

On Fri, Dec 09, 2016 at 02:36:38PM -0800, Guenter Roeck wrote: > On Fri, Dec 09, 2016 at 05:20:29PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.14 release. > > There are 45 patches in this series, all will be posted as a response > > to this one.

Re: [kernel-hardening] [PATCH] siphash: add cryptographically secure hashtable function

On Fri, Dec 09, 2016 at 07:36:59PM +0100, Jason A. Donenfeld wrote: > SipHash is a 64-bit keyed hash function that is actually a > cryptographically secure PRF, like HMAC. Except SipHash is super fast, > and is meant to be used as a hashtable keyed lookup function. > > SipHash isn't just some new

Re: [PATCH v2] USB: EHCI: spear: fix code warnings

On Thu, Dec 08, 2016 at 10:40:11PM +, csmanjuvi...@gmail.com wrote: > From: Manjunath Goudar > > This patch will fix the checkpatch.pl following warnings > WARNING: Block comments should align the * on each line > WARNING: space prohibited before semicolon I've said

Re: [PATCH] siphash: add cryptographically secure hashtable function

On 9 December 2016 at 19:36, Jason A. Donenfeld wrote: > SipHash is a 64-bit keyed hash function that is actually a > cryptographically secure PRF, like HMAC. Except SipHash is super fast, > and is meant to be used as a hashtable keyed lookup function. > > SipHash isn't just some

[PATCH] ASoC: samsung: Remove tests of member address

The driver was checking for non-NULL address of struct's members: - s3c_audio_pdata->type (union), - s3c_audio_pdata->type.i2s (embedded struct). This is pointless as these will be always non-NULL. The 's3c_audio_pdata' is always initialized in static memory so it will be zeroed. Additionally

[PATCH] HID: asus: Fix keyboard support

The previous submission which added Touchpad support broke the Keyboard support of this driver. This patch: 1. fixes the Keyboard support (by assigning drvdata->input); 2. renames NOTEBOOK_QUIRKS to KEYBOARD_QUIRKS; 3. adds the NO_INIT_REPORT quirk to the KEYBOARD_QUIRKS; and 4. sets the

[PATCH net-next] net: mvneta: select GENERIC_ALLOCATOR

We previously relied on GENERIC_ALLOCATOR to be selected by CONFIG_ARM, but now we can compile-test the driver on other architectures that don't select it: drivers/net/built-in.o: In function `mvneta_bm_remove': mvneta_bm.c:(.text+0x4ee35): undefined reference to `gen_pool_free' This adds an

Re: [PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers

On Fri, Dec 09, 2016 at 04:21:48PM -0800, Stephen Hemminger wrote: > On Fri, 9 Dec 2016 22:35:05 + > Haiyang Zhang wrote: > > > > > > > > > > > Emulated NIC is already excluded in start of netvc notifier handler. > > > > > > > > > > static int

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On Sat, Dec 10, 2016 at 08:27:57PM +0800, Baoquan He wrote: > Whether CONFIG_RANDOMIZE_BASE is yes or not, with 'nokaslr' specified, > Kernel text mapping size should be 512M, just the same as no kaslr code > compiled in. "should be" still doesn't really explain what the problem is. What's wrong

Re: [kernel-hardening] Re: Remaining crypto API regressions with CONFIG_VMAP_STACK

Why did you drop me from the CC list when you were replying to my email? Eric Biggers wrote: > On Sat, Dec 10, 2016 at 01:32:08PM +0800, Herbert Xu wrote: > >> Are you sure? Any instance of *_ON_STACK must only be used with >> sync algorithms and most drivers under

Re: [PATCH V1] pinctrl:pxa:pinctrl-pxa2xx:- No need of devm functions

Arvind Yadav writes: Hi Arvind, > In functions pxa2xx_build_functions, the memory allocated for > 'functions' is live within the function only. After the > allocation it is immediately freed with devm_kfree. There is > no need to allocate memory for 'functions' with

Assalamu`Alaikum.

Dear Sir/Madam. Assalamu`Alaikum. I am Dr mohammad ouattara, I have ($10.6 Million us dollars) to transfer into your account, I will send you more details about this deal and the procedures to follow when I receive a positive response from you, Have a great day, Dr mohammad ouattara.

Re: [PATCH] driver core: flush async calls before testing driver removal

Hello Dmitry, On 12/10/2016 03:59 AM, Dmitry Torokhov wrote: > On Fri, Dec 9, 2016 at 4:15 PM, Vladimir Zapolskiy wrote: >> If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false >> positives are reported for ATA controller drivers, because ATA port >> probes are

Re: [RFC 0/5] rcu: Introduce leaf_node_for_each_mask_possible_cpu() and its friend

On Fri, Dec 09, 2016 at 08:28:05PM -0800, Paul E. McKenney wrote: > On Sat, Dec 10, 2016 at 08:45:38AM +0800, Boqun Feng wrote: > > On Fri, Dec 09, 2016 at 03:49:45PM -0800, Paul E. McKenney wrote: > > > On Fri, Dec 09, 2016 at 04:48:22PM +0800, Boqun Feng wrote: > > > > Hi Paul, > > > > > > > >

[patch] nvme-fabrics: correct some printk information

We really don't care where "ctrl" is on the stack since we're just returning soon what we want is the actual ctrl pointer itself. Signed-off-by: Dan Carpenter diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c index 771e2e761872..e6395ed2f562 100644 ---

Re: [PATCH 1/1 linux-next] fs: add BLOCKSIZE(inode)

Hi Fabian, [auto build test WARNING on next-20161209] url: https://github.com/0day-ci/linux/commits/Fabian-Frederick/fs-add-BLOCKSIZE-inode/20161210-171013 config: x86_64-acpi-redef (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached

Re: [patch] nvme-fabrics: correct some printk information

On Sat, 2016-12-10 at 12:06 +0300, Dan Carpenter wrote: > We really don't care where "ctrl" is on the stack since we're just > returning soon what we want is the actual ctrl pointer itself. > > Signed-off-by: Dan Carpenter > > diff --git a/drivers/nvme/host/fc.c

Re: Misalignment, MIPS, and ip_hdr(skb)->version

Felix Fietkau writes: > On 2016-12-07 19:54, Jason A. Donenfeld wrote: >> On Wed, Dec 7, 2016 at 7:51 PM, David Miller wrote: >>> It's so much better to analyze properly where the misalignment comes from >>> and address it at the source, as we have for

[PATCH 1/7] ARM: EXYNOS: Constify list of retention registers

The list of retention registers (release_ret_regs field of struct exynos_pm_data and arrays with values) are not modified and can be made const to improve the const safeness. Signed-off-by: Krzysztof Kozlowski --- arch/arm/mach-exynos/suspend.c | 8 1 file changed, 4

[tip:x86/cleanups] x86/ldt: Make a size argument unsigned

Commit-ID: 296dc5806de57dc84fce000d60fc201ba40f96e8 Gitweb: http://git.kernel.org/tip/296dc5806de57dc84fce000d60fc201ba40f96e8 Author: Dan Carpenter AuthorDate: Thu, 8 Dec 2016 13:56:03 +0300 Committer: Thomas Gleixner CommitDate: Sat, 10

Re: [PATCH v4 2/2] perf probe: add sdt probes arguments into the uprobe cmd string

On Fri, 9 Dec 2016 12:14:30 -0300 Arnaldo Carvalho de Melo wrote: > Em Wed, Dec 07, 2016 at 12:26:10PM +0900, Masami Hiramatsu escreveu: > > Hello Alexis, > > > > On Sat, 26 Nov 2016 01:58:03 +0100 > > Alexis Berlemont wrote: > > > > > An sdt probe

Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm

On Fri, Dec 09, 2016 at 11:46:54PM +0100, Dodji Seketeli wrote: > Hello, > > Nicholas Piggin a écrit: > > [...] > > > That said, a dwarf based checker tool should be able to do as good a job > > (maybe a bit better because report is very informative and it may pick up > >

Re: [PATCH] driver core: flush async calls before testing driver removal

On Sat, Dec 10, 2016 at 02:38:41PM +0200, Vladimir Zapolskiy wrote: > Hello Greg, > > On 12/10/2016 09:32 AM, Greg Kroah-Hartman wrote: > > On Sat, Dec 10, 2016 at 02:15:19AM +0200, Vladimir Zapolskiy wrote: > >> If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false > >>

Re: Still OOM problems with 4.9er kernels

On 09.12.2016 22:42, Vlastimil Babka wrote: On 12/09/2016 07:01 PM, Gerhard Wiesinger wrote: On 09.12.2016 18:30, Michal Hocko wrote: On Fri 09-12-16 17:58:14, Gerhard Wiesinger wrote: On 09.12.2016 17:09, Michal Hocko wrote: [...] [97883.882611] Mem-Info: [97883.883747] active_anon:2915

Re: [PATCH] tty: serial: fsl_lpuart: potential NULL dereference

On Sat, Dec 10, 2016 at 01:30:36AM +0300, Alexey Khoroshilov wrote: > tty_port_tty_get() might return a tty which is NULL > if the port is not associated with a tty > (e.g. due to close or hangup). > But lpuart_start_rx_dma() dereferences tty without any check. Are you sure that tty could ever be

Re: [kernel-hardening] Re: Remaining crypto API regressions with CONFIG_VMAP_STACK

Hi Herbert, On Sat, Dec 10, 2016 at 6:37 AM, Herbert Xu wrote: > As for AEAD we never had a sync interface to begin with and I > don't think I'm going to add one. That's too bad to hear. I hope you'll reconsider. Modern cryptographic design is heading more and more

Re: [Question] New mmap64 syscall?

On Sat 2016-12-10 10:10:01, Pavel Machek wrote: > Hi! > > > > Most of these advantages should eventually go away, when struct-reorg > > > makes > > > it way into the compiler. That said, it’s a marginal (but real) > > > improvement for a > > > subset of SPEC. > > > > > > In the real world, the

Re: [PATCHSET 0/6] perf sched timehist: Introduce --idle-hist option (v2)

On 12/8/16 7:47 AM, Namhyung Kim wrote: > Hi, > > This patchset implements the idle hist feature which analyze reason of system > idle. Sometimes I need to investigate what makes CPUs to go idle even though > I have jobs to do. It may be due to I/O, waiting on lock or whatever. > ... >

Re: [kernel-hardening] Re: Remaining crypto API regressions with CONFIG_VMAP_STACK

cc: Viro because I'm talking about iov_iter. On Sat, Dec 10, 2016 at 6:45 AM, Jason A. Donenfeld wrote: > Hi Herbert, > > On Sat, Dec 10, 2016 at 6:37 AM, Herbert Xu > wrote: >> As for AEAD we never had a sync interface to begin with and I >> don't

Re: [PATCH] Staging: iio: impedance-analyzer: ad5933: fix wrong comments

On 07/12/16 17:44, Nizam Haider wrote: > according to datasheet complete control register is of 2 bytes. > http://www.analog.com/media/en/technical-documentation/data-sheets/AD5933.pdf > > Signed-off-by: Nizam Haider Applied to the togreg branch of iio.git - initially pushed out

core.c:undefined reference to `fpu_save'

Hi Andrew, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 810ac7b7558d7830e72d8dbf34b851fce39e08b0 commit: c60f169202c7643991a8b4bfeea60e06843d5b5a arch/mn10300/kernel/fpu-nofpu.c: needs asm/elf.h

[PATCH v2 5/5] staging: lustre: headers: use proper byteorder functions in lustre_idl.h

In order for lustre_idl.h to be usable for both user land and kernel space it has to use the proper byteorder functions. Signed-off-by: James Simmons Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245 Reviewed-on: http://review.whamcloud.com/16916 Reviewed-by: Frank

[PATCH v2 4/5] staging: lustre: headers: Move functions out of lustre_idl.h

From: Ben Evans Migrate functions set/get_mrc_cr_flags, ldlm_res_eq ldlm_extent_overlap, ldlm_extent_contain, ldlm_request_bufsize, and alll the PTLRPC dump_* functions out of lustre_idl.h which is a UAPI header to the places in the kernel code they are actually used. Delete

[PATCH v2 3/5] staging: lustre: headers: sort headers affected by obdo move

From: Ben Evans It was found if you sort the headers alphabetically that it reduced patch conflicts. This patch sorts the headers alphabetically and also place linux header first, then uapi header and finally the lustre kernel headers. Signed-off-by: Ben Evans

[PATCH v2 2/5] staging: lustre: obdclass: style cleanup for obdo related functions

From: Ben Evans Change the style of lustre_get_wire_obdo and lustre_set_wire_obdo to conform to linux kernel standard. Signed-off-by: Ben Evans Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6401 Reviewed-on: http://review.whamcloud.com/16917 Reviewed-on:

Re: [PATCH v2] llist: Clarify comments about when locking is needed

On Sat, Dec 10, 2016 at 10:15 AM, Mathieu Desnoyers wrote: > - On Dec 10, 2016, at 7:03 PM, Joel Fernandes joe...@google.com wrote: > >> llist.h comments are a bit confusing about when locking is needed versus when >> it isn't. Clarify these comments a bit more

Re: [PATCH v6 4/9] dt-bindings: iio: iio-mux: document iio-mux bindings

On 06/12/16 09:18, Peter Rosin wrote: > On 2016-12-06 00:26, Rob Herring wrote: >> On Wed, Nov 30, 2016 at 09:16:58AM +0100, Peter Rosin wrote: >>> Signed-off-by: Peter Rosin >>> --- >>> .../bindings/iio/multiplexer/iio-mux.txt | 40 >>> ++ >>>

Linux 4.4.38

I'm announcing the release of the 4.4.38 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.8.14

Turns out I'm going to be on a very long flight early tomorrow morning, so I figured it would be good to get this kernel out now, instead of delaying it by an extra day. So, I'm announcing the release of the 4.8.14 kernel. All users of the 4.8 kernel series must upgrade. The updated 4.8.y git

[PATCH 1/4] [media] bt8xx: One function call less in bttv_input_init() after error detection

From: Markus Elfring Date: Sat, 10 Dec 2016 09:29:24 +0100 The kfree() function was called in one case by the bttv_input_init() function during error handling even if the passed variable contained a null pointer. This issue was detected by using the Coccinelle

[GIT PULL] overlayfs update for 4.10

Hi Al, I usually send overlayfs pulls directly to Linus, but it it suits you, please feel free to pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus This update contains: - try to clone on copy-up; - allow renaming a directory; - fix data

Re: [regression ?] kbuild: fix building bzImage with CONFIG_TRIM_UNUSED_KSYMS enabled

On Sat, 10 Dec 2016, Sergey Senozhatsky wrote: > On (12/09/16 13:07), Nicolas Pitre wrote: > [..] > > > build: > > > make -j4 > build_log 2>&1 > > > > > > package: > > > make -j4 INSTALL_MOD_PATH="${pkgdir}" modules_install >> build_log 2>&1 > > > > Weird. > > it is. sorry for long reply, it

[PATCH] mm: fadvise: avoid expensive remote LRU cache draining after FADV_DONTNEED

When FADV_DONTNEED cannot drop all pages in the range, it observes that some pages might still be on per-cpu LRU caches after recent instantiation and so initiates remote calls to all CPUs to flush their local caches. However, in most cases, the fadvise happens from the same context that

Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null)

On Sat, Dec 10, 2016 at 11:04:44AM -0600, Josh Poimboeuf wrote: > That's a new one. Was there anything else printed? It is the first line that appears in dmesg when I boot: [0.00] WARNING: kernel stack frame pointer at b5e03f40 in swapper:0 has bad value (null) [

Re: [PATCH v2] llist: Clarify comments about when locking is needed

- On Dec 10, 2016, at 7:03 PM, Joel Fernandes joe...@google.com wrote: > llist.h comments are a bit confusing about when locking is needed versus when > it isn't. Clarify these comments a bit more by being a bit more descriptive > about why locking is needed for llist_del_first. As I stated

Re: [PATCH v2 3/5] staging: lustre: headers: sort headers affected by obdo move

On Sat, Dec 10, 2016 at 01:05:59PM -0500, James Simmons wrote: > From: Ben Evans > > It was found if you sort the headers alphabetically > that it reduced patch conflicts. This patch sorts > the headers alphabetically and also place linux > header first, then uapi header and

Re: [patch] nvme-fabrics: correct some printk information

On Sat, Dec 10, 2016 at 03:27:50AM -0800, Joe Perches wrote: > On Sat, 2016-12-10 at 12:06 +0300, Dan Carpenter wrote: > > We really don't care where "ctrl" is on the stack since we're just > > returning soon what we want is the actual ctrl pointer itself. > > > > Signed-off-by: Dan Carpenter

[PATCH] block: allow WRITE_SAME commands with the SG_IO ioctl

The WRITE_SAME commands are not present in the blk_default_cmd_filter write_ok list, and thus are failed with -EPERM when the SG_IO ioctl() is executed without CAP_SYS_RAWIO capability (e.g., unprivileged users). [ sg_io() -> blk_fill_sghdr_rq() > blk_verify_command() -> -EPERM ] The problem can

Re: [PATCH] iio: adc: max1027: allocate DMA-safe buffer

On Sat, Dec 10, 2016 at 05:36:34PM +, Jonathan Cameron wrote: > On 09/12/16 10:24, Marcus Folkesson wrote: > > The buffer needs to be DMA-safe when used with spi_read() > > > > Signed-off-by: Marcus Folkesson > Please read the documentation in include/linux/gfp.h

Re: [PATCH] siphash: add cryptographically secure hashtable function

> There's a 32-bit secret random salt (inet_ehash_secret) which means > that in practice, inet_ehashfn() will select 1 out of 2^32 different > hash functions at random each time you boot the kernel; without > knowing which one it selected, how can a local or remote attacker can > force IPv4

Could we have request_firmware_nowait with FW_OPT_NO_WARN?

Hi, In brcmfmac we use request_firmware_nowait and if fetching firmware with NVRAM variables fails then we try to fallback to the platform one (see brcmf_fw_request_code_done & brcmf_fw_request_nvram_done). Some problem for us is that on devices with platform NVRAM we get this error: Direct

WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null)

Hey, I see the line in $Subject on rc8+tip/master. Fixed already? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.

Re: enabling COMPILE_TEST support for GCC plugins in v4.11

On Fri, 9 Dec 2016 11:12:18 -0800 Kees Cook wrote: > On Fri, Dec 9, 2016 at 2:40 AM, Arnd Bergmann wrote: > > On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote: > > > >> If you have a moment, applying 215e2aa6c024[1] and reverting > >>

Re: [PATCH] iio: adc: max1027: allocate DMA-safe buffer

On 09/12/16 10:24, Marcus Folkesson wrote: > The buffer needs to be DMA-safe when used with spi_read() > > Signed-off-by: Marcus Folkesson Please read the documentation in include/linux/gfp.h about GFP_DMA. Specifically: 220 * GFP_DMA exists for historical reasons

Re: [PATCH v12 0/5] mxs-lradc: Split driver into MFD

On 09/12/16 21:08, Ksenija Stanojevic wrote: > Split existing driver mxs-lradc into MFD with touchscreen and > IIO part. > > Tested on I.MX28 Hi All, At first glance it looks like this is over to Dmitry and Lee. If they are both happy... Lee, I'm assuming this whole lot will go through MFD.

Re: [PATCH] iio: misc: add a generic regulator driver

On 06/12/16 11:12, Bartosz Golaszewski wrote: > 2016-12-03 10:11 GMT+01:00 Jonathan Cameron : >> On 30/11/16 10:10, Lars-Peter Clausen wrote: >>> On 11/29/2016 04:35 PM, Bartosz Golaszewski wrote: 2016-11-29 16:30 GMT+01:00 Lars-Peter Clausen : > On

Re: [PATCH v2 5/5] staging: lustre: headers: use proper byteorder functions in lustre_idl.h

On Sat, Dec 10, 2016 at 01:06:01PM -0500, James Simmons wrote: > In order for lustre_idl.h to be usable for both user > land and kernel space it has to use the proper > byteorder functions. Why would userspace need/want all of these inline functions? A uapi header file should just have a the

[GIT PULL] vfs prep for overlayfs update

Hi Al, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git vfs-ovl These are the bits of the upcoming overlayfs update that touch vfs/mm/af_unix. - Revert d_real_inode() comparisons that became obsolete; - add support for clone on copy-up; - add support for

Re: [patch] nvme-fabrics: correct some printk information

For my check, most of the results fall into three categories. 1) False positives (40% of results) 2) Badly designed interfaces that take a pointer to a pointer for no reason and can be cleaned up. (5%) 3) Bugs where we modified the code, but haven't tested it. Most of the time passing the

[PATCH 4/4] [media] bt8xx: Less function calls in dst_ca_ioctl() after error detection

From: Markus Elfring Date: Sat, 10 Dec 2016 21:30:10 +0100 The kfree() function was called in up to three cases by the dst_ca_ioctl() function during error handling even if the passed variable contained a null pointer. This issue was detected by using the

RE: ATH9 driver issues on ARM64

Hi, After taking some more lecroy traces, we see that after 2nd ASSERT from EP on ARM64 we see continuous data movement of 32 dwords or 12 dwords and never sign of DEASSERT. Comparatively on working traces (x86) after 2nd assert there are only BAR register reads and writes and then DEASSERT,

Re: [PATCH v2 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

On Sat, Dec 10, 2016 at 09:41:56PM +0800, Baoquan He wrote: > 1) Fedora 25 defaults to enable CONFIG_RANDOMIZE_BASE. And this worries > maintainers of several Fedora component. People ever asked me how to > judge whether it's a kaslr kernel. I told them I usually read elf header > of kcore -

[PATCH] remove unused parameter

Remove unused parameter in wakeup_gran function for Completely Fair Scheduling (CFS). Signed-off-by: Weiwei Jia --- kernel/sched/fair.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index c242944..f4375d4

Re: [PATCH v3 00/15] livepatch: hybrid consistency model

On Sat, Dec 10, 2016 at 04:46:17PM +1100, Balbir Singh wrote: > On Thu, 2016-12-08 at 12:08 -0600, Josh Poimboeuf wrote: > > Dusting the cobwebs off the consistency model again.  This is based on > > linux-next/master. > >  > > v1 was posted on 2015-02-09: > >  > >  

[PATCH v2] llist: Clarify comments about when locking is needed

llist.h comments are a bit confusing about when locking is needed versus when it isn't. Clarify these comments a bit more by being a bit more descriptive about why locking is needed for llist_del_first. Cc: Huang Ying Cc: Ingo Molnar Cc: Will Deacon

Re: [patch] nvme-fabrics: correct some printk information

On Sat, 10 Dec 2016, Dan Carpenter wrote: > On Sat, Dec 10, 2016 at 03:27:50AM -0800, Joe Perches wrote: > > On Sat, 2016-12-10 at 12:06 +0300, Dan Carpenter wrote: > > > We really don't care where "ctrl" is on the stack since we're just > > > returning soon what we want is the actual ctrl

Re: [Question] New mmap64 syscall?

Hi! > > Most of these advantages should eventually go away, when struct-reorg makes > > it way into the compiler. That said, it’s a marginal (but real) improvement > > for a > > subset of SPEC. > > > > In the real world, the importance of ILP32 as an aid to transition legacy > > code > > that

[PATCH v2 0/5] Fix ups to make lustre_idl.h a proper UAPI header

From: James Simmons James Simmons Fix ups to make lustre_idl.h a proper UAPI header The header lustre_idl.h is a UAPI header which contains extras that don't belong. This patch set moves a bunch of very kernel specific material out of the header. Lastly proper byteorder

[PATCH net 2/3] net: bridge: add helper to set topology change

Add a __br_set_topology_change helper to set the topology change value. This can be later extended to add actions when the topology change flag is set or cleared. Signed-off-by: Vivien Didelot --- net/bridge/br_private_stp.h | 1 + net/bridge/br_stp.c

  1   2   3   4   5   >