[PATCH v3 03/27] staging: ccree: fold reg common defines into driver

Fold the 2 macro defined in dx_reg_common.h into the file they are used in and delete the file. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_crypto_ctx.h | 4 ++-- drivers/staging/ccree/dx_reg_common.h | 13 - drivers/staging/ccree/ssi_driver.h| 5 +++-- 3

[PATCH v3 07/27] staging: ccree: tag debugfs init/exit func properly

The debugfs global init and exit functions were missing __init and __exit tags, potentially wasting memory. Fix it by properly tagging them. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_debugfs.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v3 04/27] staging: ccree: remove GFP_DMA flag from mem allocs

Remove bogus GFP_DMA flag from memory allocations. ccree driver does not operate over an ISA or similar limited bus. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_cipher.c | 2 +- drivers/staging/ccree/ssi_hash.c | 15 ++- 2 files changed, 7 insertions(+), 10

[PATCH v3 02/27] staging: ccree: fold hash defs into queue defs

Fold the two remaining enum in hash defs into the queue defs that are using them and delete the hash defs include file. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_hw_queue_defs.h | 13 + drivers/staging/ccree/hash_defs.h| 23 ---

[PATCH v3 05/27] staging: ccree: pick alloc mem flags based on req flags

The ccree driver was allocating memory using GFP_KERNEL flag always, ignoring the flags set in the crypto request. Fix it by choosing gfp flags based on crypto request flags. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_buffer_mgr.c | 19 +++--

[PATCH v3 08/27] staging: ccree: remove unused leftover field

Remove the unused monitor_desc field. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_request_mgr.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/ccree/ssi_request_mgr.c b/drivers/staging/ccree/ssi_request_mgr.c index 7686e14..e1c01da 100644 ---

[PATCH v3 06/27] staging: ccree: copy larval digest from RAM

The ccree driver was using a DMA operation to copy larval digest from the ccree SRAM to RAM. Replace it with a simple memcpy. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_driver.c | 2 + drivers/staging/ccree/ssi_hash.c | 121 -

[PATCH v3 09/27] staging: ccree: break send_request and fix ret val

The send_request() function was handling both synchronous and asynchronous invocations, but were not handling the asynchronous case, which may be called in an atomic context, properly as it was sleeping. Start to fix the problem by breaking up the two use cases to separate functions calling a

[PATCH v3 13/27] staging: ccree: check DMA pool buf !NULL before free

If we ran out of DMA pool buffers, we get into the unmap code path with a NULL before. Deal with this by checking the virtual mapping is not NULL. Cc: sta...@vger.kernel.org Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_buffer_mgr.c | 3 ++- 1 file changed, 2 insertions(+), 1

[PATCH v3 11/27] stating: ccree: revert "staging: ccree: fix leak of import() after init()"

This reverts commit c5f39d07860c ("staging: ccree: fix leak of import() after init()") and commit aece09024414 ("staging: ccree: Uninitialized return in ssi_ahash_import()"). This is the wrong solution and ends up relying on uninitialized memory, although it was not obvious to me at the time.

[PATCH v3 10/27] staging: ccree: add backlog processing

Crypto API tfm providers are required to provide a backlog service, if so indicated, that queues up requests in the case of the provider being busy and processing them later. The ccree driver did not provide this facility. Add it now. Signed-off-by: Gilad Ben-Yossef ---

[PATCH v3 12/27] staging: ccree: failing the suspend is not an error

PM suspend returning a none zero value is not an error. It simply indicates a suspend is not advised right now so don't treat it as an error. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_request_mgr.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git

[PATCH v3 17/27] staging: ccree: use array for double buffer

The ccree hash code is using a double buffer to hold data for processing but manages the buffers and their associated data count in two separate fields and uses a predicate to chose which to use. Move to using a proper 2 members array for a much cleaner code. Signed-off-by: Gilad Ben-Yossef ---

[PATCH v3 15/27] staging: ccree: use Makefile to include PM code

Replace ugly ifdefs with some inline macros and Makefile magic for optionally including power management related code for better readability. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/Makefile | 3 ++- drivers/staging/ccree/ssi_pm.c | 9 +---

[PATCH v3 14/27] staging: ccree: handle end of sg list gracefully

If we are asked for number of entries of an offset bigger than the sg list we should not crash. Cc: sta...@vger.kernel.org Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_buffer_mgr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v3 18/27] staging: ccree: allocate hash bufs inside req ctx

Move to allocating the buffers needed for requests as part of the request structure instead of malloc'ing each one on it's own, making for simpler (and more efficient) code. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_hash.c | 68

[PATCH v3 16/27] staging: ccree: remove unused field

Remove unused struct field. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_hash.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/ccree/ssi_hash.c b/drivers/staging/ccree/ssi_hash.c index ee7370c..efea792 100644 --- a/drivers/staging/ccree/ssi_hash.c +++

[PATCH v3 21/27] staging: ccree: fold common code into service func

Fold common code in hash call into service functions. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_hash.c | 339 ++- 1 file changed, 116 insertions(+), 223 deletions(-) diff --git a/drivers/staging/ccree/ssi_hash.c

[PATCH v3 20/27] staging: ccree: fix indentation of func params

Fix indentation of some function params in hash code for better readability. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_hash.c | 46 +--- 1 file changed, 20 insertions(+), 26 deletions(-) diff --git a/drivers/staging/ccree/ssi_hash.c

[PATCH v3 19/27] staging: ccree: do not map bufs in ahash_init

hash_init was mapping DMA memory that were then being unmap in hash_digest/final/finup callbacks, which is against the Crypto API usage rules (see discussion at https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg30077.html) Fix it by moving all buffer mapping/unmapping or each Crypto

[PATCH v3 22/27] staging: ccree: put pointer next to var name

Put pointer next to var name as per coding style. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_request_mgr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ccree/ssi_request_mgr.c b/drivers/staging/ccree/ssi_request_mgr.c index

[PATCH v3 23/27] stating: ccree: fix allocation of void sized buf

We were allocating buffers using sizeof(*struct->field) where field was type void. Fix it by having a local variable with the real type. Cc: sta...@vger.kernel.org Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_ivgen.c| 9 - drivers/staging/ccree/ssi_sram_mgr.c | 9

[PATCH v3 26/27] staging: ccree: update TODO

Update TODO to reflect work done Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/TODO | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/ccree/TODO b/drivers/staging/ccree/TODO index 6d8702b..b8e163d 100644 --- a/drivers/staging/ccree/TODO +++

[PATCH v3 25/27] staging: ccree: remove unneeded includes

Remove include files not needed for compilation. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_aead.c| 7 --- drivers/staging/ccree/cc_buffer_mgr.c | 6 -- drivers/staging/ccree/cc_cipher.c | 4 drivers/staging/ccree/cc_driver.c | 31

[PATCH v3 27/27] staging: ccree: add missing include

Add the missing include of include file with function declarations. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/cc_debugfs.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/ccree/cc_debugfs.c b/drivers/staging/ccree/cc_debugfs.c index f927a73..08f8db4 100644

Re: [PATCH v3 01/13] x86/retpoline: Add initial retpoline support

On Sun, 2018-01-07 at 12:46 +0100, Borislav Petkov wrote: > > >  > > The other fun one for alternatives is in entry_64.S, where we really > > need the return address of the call instruction to be *precisely* the  > > .Lentry_SYSCALL_64_after_fastpath_call label, so we have to eschew the > >

Re: Proposal: CAP_PAYLOAD to reduce Meltdown and Spectre mitigation costs

On Sun, Jan 07, 2018 at 11:16:28AM +0200, Avi Kivity wrote: > I think capabilities will work just as well with cgroups. The container > manager will set CAP_PAYLOAD to payload containers; and if those run an init > system or a container manager themselves, they'll drop CAP_PAYLOAD for all >

Re: Proposal: CAP_PAYLOAD to reduce Meltdown and Spectre mitigation costs

07.01.2018, 15:29, "Theodore Ts'o" : > On Sun, Jan 07, 2018 at 11:16:28AM +0200, Avi Kivity wrote: >>  I think capabilities will work just as well with cgroups. The container >>  manager will set CAP_PAYLOAD to payload containers; and if those run an init >>  system or a container manager

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > On Sun 07-01-18 10:11:15, Greg KH wrote: > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > 4.14-stable review patch. If anyone has any objections,

Re: [PATCH v4 19/19] fs: handle inode->i_version more efficiently

On Fri, Dec 22, 2017 at 1:05 PM, Jeff Layton wrote: > From: Jeff Layton > > Since i_version is mostly treated as an opaque value, we can exploit that > fact to avoid incrementing it when no one is watching. With that change, > we can avoid incrementing the counter on writes, unless someone has >

Re: Proposal: CAP_PAYLOAD to reduce Meltdown and Spectre mitigation costs

On 01/07/2018 02:29 PM, Theodore Ts'o wrote: On Sun, Jan 07, 2018 at 11:16:28AM +0200, Avi Kivity wrote: I think capabilities will work just as well with cgroups. The container manager will set CAP_PAYLOAD to payload containers; and if those run an init system or a container manager

Re: [alsa-devel][PATCH v7] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

On Fri, Jan 05, 2018 at 12:38:03PM +, Mark Brown wrote: > This doesn't apply cleanly against current code, what did you submit > against? :( These aren't trivial things that have just been added to > my tree in this development cycle either, it looks like you're > submitting against some

Re: [RFCv2 2/4] Documentation: document nospec helpers

On Sat, Jan 06, 2018 at 09:20:59PM -0800, Randy Dunlap wrote: > On 01/05/18 06:57, Mark Rutland wrote: > > Document the rationale and usage of the new nospec*() helpers. > > > > Signed-off-by: Mark Rutland > > Signed-off-by: Will Deacon > > Cc: Dan Williams > > Cc: Jonathan Corbet > > Cc:

[GIT PULL] LED fix for 4.15-rc7

Hi Linus, Please pull LED regression fix for 4.15-rc7. The commit 2b83ff96f51d for 4.15-rc6, which was fixing LED brightness setting after clearing delay_off broke the behavior on any alteration of delay_on{off} properties, due to use of a LED core helper that does too much for this particular

Re: [PATCH] i2c: core: report OF style module alias for devices registered via OF

Hello Wolfram, On Sun, Dec 3, 2017 at 10:40 PM, Javier Martinez Canillas wrote: > The buses should honor the firmware interface used to register the device, > but the I2C core reports a MODALIAS of the form i2c: even for I2C > devices registered via OF. > > This means that user-space will never

Re: [PATCH v3 1/1] runchecks: Generalize make C={1,2} to support multiple checkers

On Sun, 2018-01-07 at 13:03 +0100, Philippe Ombredanne wrote: > Knut, > > On Fri, Jan 5, 2018 at 3:30 PM, Jani Nikula > wrote: > > On Thu, 04 Jan 2018, Knut Omang wrote: > >> On Thu, 2018-01-04 at 17:50 +0200, Jani Nikula wrote: > >>> On Thu, 04 Jan 2018, Knut Omang wrote: > >>> > Add

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > >

[PATCH v2 0/2] video-UDLFB: Adjustments for dlfb_realloc_framebuffer()

From: Markus Elfring Date: Sun, 7 Jan 2018 14:24:34 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Return an error code only as a constant Delete an error message for a failed memory allocation --- v2: Rebased on Linux

[PATCH v2 1/2] video: udlfb: Return an error code only as a constant in dlfb_realloc_framebuffer()

From: Markus Elfring Date: Sun, 7 Jan 2018 14:02:36 +0100 * Return an error code without storing it in an intermediate variable. * Delete the label "error" and local variable "retval" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring --- v2: This update

[PATCH v2 2/2] video: udlfb: Delete an error message for a failed memory allocation in dlfb_realloc_framebuffer()

From: Markus Elfring Date: Sun, 7 Jan 2018 14:07:36 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- v2: This update suggestion was rebased on source files from the

[PATCH] Revert "ARM: dts: bcm283x: Fix DTC warnings about missing phy-cells"

This reverts commit 014d6da6cb2525d7f48fb08c705cb130cc7b5f4a. The DT clean up could trigger an endless deferred probe of DWC2 USB driver on the Raspberry Pi 2/3. So revert the change until we fixed the probing issue. Signed-off-by: Stefan Wahren --- Hi Arnd, hi Olof, i hope this has a chance

[PATCH] soc: imx: gpc: de-register power domains only if initialized

If power domain information are missing in the device tree, no power domains get initialized. However, imx_gpc_remove tries to remove power domains always in the old DT binding case. Only remove power domains when imx_gpc_probe initialized them in first place. Fixes: 721cabf6c660 ("soc: imx: move

[GIT PULL] apparmor fix for 4.15-rc7

Linus, can you please pull the following regression fix for apparmor. It fixes a regression when the kernel feature set is reported as supporting mount and policy is pinned to a feature set that does not support mount mediation. thanks -- John The following changes since commit

Re: [PATCH 06/18] x86, barrier: stop speculation for failed access_ok

> > 2. It is very very complicated to answer a question like "is > > sequence x safe on all of vendor's microprocessors" even for the vendor > > so far "is sequence x safe" was viewed by cpu vendors as > "is sequence x going to stop speculative execution". Incorrect. Modern processors are

Re: Avoid speculative indirect calls in kernel

> I disagree. When there are patches that slow execution down up to 30%, > I want to be able to mark a binary as "trusted" so that I can run it It's not a binary that is trusted - it's a binary in a given use case. You could easily have the same binary being run in two situations on the same box

Re: [PATCH v3 01/13] x86/retpoline: Add initial retpoline support

On Sun, Jan 07, 2018 at 12:21:29PM +, David Woodhouse wrote: > http://git.infradead.org/users/dwmw2/linux-retpoline.git > > In particular, this call site in entry_64.S: > http://git.infradead.org/users/dwmw2/linux-retpoline.git/blob/0f5c54a36e:/arch/x86/entry/entry_64.S#l270 > > It's still

[PATCH] spi: imx: do not access registers while clocks disabled

Since clocks are disabled except during message transfer clocks are also disabled when spi_imx_remove gets called. Accessing registers leads to a freeeze at least on a i.MX 6ULL. Enable clocks before disabling accessing the MXC_CSPICTRL register. Fixes: 9e556dcc55774 ("spi: spi-imx: only enable

Re: Avoid speculative indirect calls in kernel

On Fri, Jan 05, 2018 at 08:13:33AM +0100, Willy Tarreau wrote: > I'm not fond of running the mitigations, but given that a few sysops can > connect to the machine to collect stats or counters, I think it would be > better to ensure these people can't happily play with the exploits to > dump stuff

Re: [PATCH v2 5/7] dt-bindings: i3c: Document core bindings

Hi Rob, On Tue, 26 Dec 2017 12:29:34 -0600 Rob Herring wrote: > >> > > > +Optional properties > >> > > > +--- > >> > > > +- reg: static address. Only valid is the device has a static > >> > > > address. > >> > > > +- i3c-dynamic-address: dynamic address to be assigned to this

Re: [PATCH 4.4 00/37] 4.4.110-stable review

Hi Greg, I cloned and built suse12, and it does not have issues with EFI + PTI (kaiser) on my machine. BTW, i have also reproduced this problem on another machine with the same configuration, therefore, it is not specific only to one box. Also, as I mentioned earlier I am seeing the same issue

[alsa-devel][PATCH v8] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

Currently there is no support for TSCS42xx audio CODECs. Add support for TSCS42xx audio CODECs. Reviewed-by: Charles Keepax Acked-by: Philippe Ombredanne Signed-off-by: Steven Eckhoff --- Thank you to everyone involved in improving this driver. In the following history I have attempted to

Cache-controlling kernel APIs for user-space programs to defeat Meltdown/Spectre and to make more secure applications portably

I've been thinking that the problem that makes Meltdown/Spectre possible is a synchronization problem between the use of the cache by all running processes and invalidating the cache when switching tasks so that the contents of the cache for a process don't exist when switching and running to

Re: Proposal: CAP_PAYLOAD to reduce Meltdown and Spectre mitigation costs

> I'm interested in participating to working on such a solution, given > that haproxy is severely impacted by "pti=on" and that for now we'll > have to run with "pti=off" on the whole system until a more suitable > solution is found. I'm still trying to work out what cases there are for this. I

[PATCH] x86: Unify definition of jiffies

jiffies_64 is always defined in file kernel/time/timer.c. Thus, we can unify definition of jiffies and make it less confusing. This only affects 64-bit platforms. Signed-off-by: Zhihui Zhang --- arch/x86/kernel/time.c| 4 arch/x86/kernel/vmlinux.lds.S | 4 ++-- 2 files changed, 2

[PATCH] ixgbevf: use ARRAY_SIZE for various array sizing calculations

From: Colin Ian King Use the ARRAY_SIZE macro on various arrays to determine size of the arrays. Improvement suggested by coccinelle. Signed-off-by: Colin Ian King --- drivers/net/ethernet/intel/ixgbevf/vf.c | 17 +++-- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git

Re: [PATCH] zsmalloc: use U suffix for negative literals being shifted

Hello, Sorry for the delay. I have missed this until now. ;-( On Sun, Dec 24, 2017 at 11:33 AM, Nick Desaulniers wrote: > Fixes warnings about shifting unsigned literals being undefined > behavior. > > Signed-off-by: Nick Desaulniers > --- > mm/zsmalloc.c | 2 +- > 1 file changed, 1

Re: [PATCH 4.4 00/37] 4.4.110-stable review

Hi Greg, I reverted suse12 back to: 13dae54cb229d078635f159dd8afe16ae683980b x86/kaiser: Move feature detection up (bsc#1068032). And, still do not see the problem. So, whatever fixes the issue comes before kaiser. Pavel On Sun, Jan 7, 2018 at 9:17 AM, Pavel Tatashin wrote: > Hi Greg, > > I

[PATCH] staging: iio: light: Add breaks to lengthy lines

This fixes three instances of checkpatch warning: WARNING: line over 80 characters Signed-off-by: George Edward Bulmer --- drivers/staging/iio/light/tsl2x7x.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/drivers/staging/iio/light/tsl2x7x.c

RE: [RFC PATCH 13/12] Retpoline vs. CONFIG_TRIM_UNUSED_SYMBOLS

Sure, I can use __x86_indirect_thunk_rax. H.J. > -Original Message- > From: David Woodhouse [mailto:dw...@infradead.org] > Sent: Sunday, January 07, 2018 12:03 AM > To: Andi Kleen ; Van De Ven, Arjan > ; Lu, Hongjiu ; > Tsimbalist, Igor V > Cc: Paul Turner ; LKML ; > Linus Torvalds ;

Re: Proposal: CAP_PAYLOAD to reduce Meltdown and Spectre mitigation costs

On 01/07/2018 04:36 PM, Alan Cox wrote: I'm interested in participating to working on such a solution, given that haproxy is severely impacted by "pti=on" and that for now we'll have to run with "pti=off" on the whole system until a more suitable solution is found. I'm still trying to work

Re: atm/clip: Use seq_puts() in svc_addr()

On Sun, 7 Jan 2018 09:19:17 +0100 SF Markus Elfring wrote: > >> Two strings should be quickly put into a sequence by two function calls. > >> Thus use the function "seq_puts" instead of "seq_printf". > >> > >> This issue was detected by using the Coccinelle software. > > > > Can you please

Re: dvb usb issues since kernel 4.9

On Sun, 7 Jan 2018, Mauro Carvalho Chehab wrote: > > > It seems that the original patch were designed to solve some IRQ issues > > > with network cards with causes data losses on high traffic. However, > > > it is also causing bad effects on sustained high bandwidth demands > > > required by DVB

Re: [PATCH v6 10/10] clocksource: timer-dm: Check prescaler value

On 1/5/2018 4:17 AM, Ladislav Michl wrote: On Tue, Jan 02, 2018 at 03:39:59PM +0530, Keerthy wrote: From: Ladislav Michl Invalid prescaler value is silently ignored. Fix that by returning -EINVAL in such case. As invalid value disabled use of the prescaler, use -1 explicitely for that

Re: [PATCH v6 00/10] omap: dmtimer: Move driver out of plat-omap

On 1/2/2018 3:39 PM, Keerthy wrote: The series moves dmtimer out of plat-omap to drivers/clocksource. The series also does a bunch of changes to pwm-omap-dmtimer code to adapt to the driver migration and clean up plat specific pdata-quirks and use the dmtimer platform data. Boot tested on

[PATCH v3 0/3] video-SMSC UFX: Adjustments for two function implementations

From: Markus Elfring Date: Sun, 7 Jan 2018 16:54:32 +0100 Three update suggestions were taken into account from static source code analysis. Markus Elfring (3): Less checks in ufx_usb_probe() after error detection Return an error code only as a constant in ufx_realloc_framebuffer()

[PATCH v3 1/3] video: smscufx: Less checks in ufx_usb_probe() after error detection

From: Markus Elfring Date: Sun, 7 Jan 2018 15:56:11 +0100 Up to four checks could be repeated by the ufx_usb_probe() function during error handling even if the relevant properties can be determined for the involved variables before by source code analysis. * Return directly after a call of the

[PATCH 00/12] perf: Assorted fixes

hi, sending assorted general fixes that queued up in my other branches. Also available in here: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git perf/fixes thanks, jirka --- include/uapi/linux/perf_event.h | 10 +--- kernel/events/callchain.c|

[PATCH 03/12] perf: Allocate context task_ctx_data for child event

Currently we use perf_event_context::task_ctx_data to save and restore the LBR status when the task is scheduled out and in. We don't allocate it for child contexts, which results in shorter task's LBR stack, because we don't save the history from previous run and start over every time we

[PATCH 05/12] perf: Make perf_callchain function static

And moving it into core.c, because there's no caller of this function other than the one in core.c Link: http://lkml.kernel.org/n/tip-uqp7qd6aif47g39glnbu9...@git.kernel.org Signed-off-by: Jiri Olsa --- kernel/events/callchain.c | 15 --- kernel/events/core.c | 16

[PATCH 09/12] perf script: Add support to display lost events

Adding option to display lost events: $ perf script --show-lost-events ... mplayer 13810 [002] 468011.402396:100 cycles:ppp: ff.. mplayer 13810 [002] 468011.402396: PERF_RECORD_LOST lost 3880 mplayer 13810 [002] 468011.402397:100 cycles:ppp: ff.. Link:

[PATCH 01/12] perf tools: Enable LIBBABELTRACE by default

There's no reason anymore to treat babel trace in a special way, because a) we no longer display its state b) the needed babeltrace library is now out and well adopted among distros. Link: http://lkml.kernel.org/n/tip-n1c2a8hwtf6wlh8e0uiqn...@git.kernel.org Signed-off-by: Jiri Olsa ---

[PATCH 12/12] perf report: Add --task option to display monitored tasks

Adding --task option to display monitored tasks stored in perf.data. Displaying pid/tid/ppid plus the command string aligned to distinguish parent and child tasks. $ perf record -a ... $ perf report --task # pid tidppid comm 0 0 -1 |swapper 2

[PATCH 11/12] perf report: Add --stat option to display quick data statistics

Adding --stat option to display quick data statistics of event numbers, without any further processing, like the one at the end of the perf report -D command. $ perf report --stat Aggregated stats: TOTAL events: 4566 MMAP events:113 LOST

[PATCH 07/12] perf: Update PERF_RECORD_MISC_* comment for perf_event_header::misc bit 13

The perf_event_header::misc bit 13 is shared on different events and next patch is adding yet another bit 13 user. Updating the comment to make it more structured and clear which events use bit 13. Suggested-by: Peter Zijlstra Link:

[PATCH 08/12] perf script: Add support to display sample misc field

Adding support to display sample misc field in form of letter for each bit: # perf script -F +misc ... sched-messaging 1414 K 28690.636582: 4590 cycles ... sched-messaging 1407 U 28690.636600: 325620 cycles ... sched-messaging 1414 K 28690.636608: 19473

[PATCH 10/12] perf tools: Make the tool's warning messages optional

I want to display the pure events status coming in the next patch and the tool's warnings are superfluous in the output. Making it optional, enabled by default. Link: http://lkml.kernel.org/n/tip-j30qvpjvbljwdq9at90cj...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/util/session.c | 6

[PATCH 06/12] perf: Return empty callchain instead of NULL

It simplifies the code a bit, because we dump the callchain even if it's empty. With 'empty' callchain we can remove all the NULL-checking code paths. Original-patch-from: Peter Zijlstra Link: http://lkml.kernel.org/n/tip-n4t869o2qc1b31v4wwvmx...@git.kernel.org Signed-off-by: Jiri Olsa ---

[PATCH v3 2/3] video: smscufx: Return an error code only as a constant in ufx_realloc_framebuffer()

From: Markus Elfring Date: Sun, 7 Jan 2018 16:07:11 +0100 * Return an error code without storing it in an intermediate variable. * Delete the label "error" and local variable "retval" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring --- v3: This update

[PATCH v3 3/3] video: smscufx: Delete an error message for a failed memory allocation in ufx_realloc_framebuffer()

From: Markus Elfring Date: Sun, 7 Jan 2018 16:12:40 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- v3: This update suggestion was rebased on source files from the

[PATCH 04/12] perf: Add sample_id to PERF_RECORD_ITRACE_START event comment

Adding missing sample_id line into PERF_RECORD_ITRACE_START event comment. Link: http://lkml.kernel.org/n/tip-v3pua3unuiif07kvxkk3w...@git.kernel.org Signed-off-by: Jiri Olsa --- include/uapi/linux/perf_event.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/uapi/linux/perf_event.h

[PATCH 02/12] perf tools: Display perf_event_attr::namespaces debug info

Display namespaces bit in -vv debug display: $ perf record -vv --namespaces ... ... perf_event_attr: size 112 ... namespaces 1 Link: http://lkml.kernel.org/n/tip-vbfkuxoiuo3tk27nvreqc...@git.kernel.org Signed-off-by: Jiri Olsa

Re: [PATCH v2] iio: adc: max9611: fix module auto-loading

On Sun, 7 Jan 2018 00:37:44 +0300 Dmitry Mastykin wrote: > On Sat, Jan 6, 2018 at 4:14 PM, Jonathan Cameron wrote: > > Are you using devicetree or some other method to instantiate the device? > > i.e. How does the kernel know it exists? > > > Yes, I'm using device-tree (in a way like in

Re: [PATCH] tools: fix cross-compile var export

[[PATCH] tools: fix cross-compile var export] On 06/01/2018 (Sat 12:16) Martin Kelly wrote: > From: Martin Kelly > > Currently in a number of Makefiles, we clobber the CC, LD, and/or STRIP env > vars > when cross-compiling, which breaks any additional flags that might be set > (such > as

Re: [PATCH v3 1/2] iio: add kernel-doc for field @owner

On Sun, 7 Jan 2018 08:56:05 +1100 "Tobin C. Harding" wrote: > When building kernel documentation sphinx emits the following warning > > warning: No description found for parameter 'owner' > > Add description for struct member 'owner'. > > Signed-off-by: Tobin C. Harding Applied to the

Re: [PATCH v3 2/2] iio: add field identifier for @use_count kernel-doc

On Sun, 7 Jan 2018 08:56:06 +1100 "Tobin C. Harding" wrote: > Kernel-doc for @use_count does not currently have a field identifier. > All the rest of the fields do. @use_count is used internally and should > not be accessed directly by the driver so it should be marked as so. > > Add [INTERN]

Re: [PATCH v2 01/27] staging: ccree: SPDXify driver

Gilad, On Sun, Jan 7, 2018 at 11:13 AM, Gilad Ben-Yossef wrote: > On Wed, Jan 3, 2018 at 5:01 PM, Philippe Ombredanne > wrote: >> Gilad, >> >> On Wed, Jan 3, 2018 at 2:35 PM, Gilad Ben-Yossef wrote: >>> Replace verbatim GPL v2 copy with SPDX tag. >>> >>> Signed-off-by: Gilad Ben-Yossef >> >>

Re: [PATCH v6 15/15] MIPS: ingenic: Initial GCW Zero support

On Fri, Jan 5, 2018 at 7:25 PM, Paul Cercueil wrote: > The GCW Zero (http://www.gcw-zero.com) is a retro-gaming focused > handheld game console, successfully kickstarted in ~2012, running Linux. > > Signed-off-by: Paul Cercueil > Acked-by: Mathieu Malaterre > --- >

[GIT PULL] parisc architecture fixes for 4.15-rc7

Hi Linus, please pull a few fixes for the parisc architecture from: git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.15-3 The fixes are: - Many small fixes to show the real physical addresses of devices instead of hashed addresses. - One important fix to

Re: [PATCH 6/7] arm64: allwinner: h6: add the basical Allwinner H6 DTSI file

On Sat, Jan 6, 2018 at 6:09 AM, Icenowy Zheng wrote: > Allwinner H6 is a new SoC with Cortex-A53 cores from Allwinner, with its > memory map fully reworked and some high-speed peripherals (PCIe, USB > 3.0) introduced. > > This commit adds the basical DTSI file of it, including the clock > support

Re: [PATCH] staging: iio: light: Add breaks to lengthy lines

On Sun, 7 Jan 2018 15:08:01 + George Edward Bulmer wrote: > This fixes three instances of checkpatch warning: > WARNING: line over 80 characters > > Signed-off-by: George Edward Bulmer Applied, thanks, Jonathan > --- > drivers/staging/iio/light/tsl2x7x.c | 9 ++--- > 1 file changed,

Re: [Y2038] [PATCH v2 03/10] compat: enable compat_get/put_timespec64 always

On Thu, Dec 14, 2017 at 3:27 PM, Ben Hutchings wrote: > On Mon, 2017-11-27 at 11:30 -0800, Deepa Dinamani wrote: >> These functions are used in the repurposed compat syscalls >> to provide backward compatibility for using 32 bit time_t >> on 32 bit systems. >> >> Signed-off-by: Deepa Dinamani >

Re: [PATCH v2 3/5] x86/mm: Centralize PMD flags in sme_encrypt_kernel()

On Thu, Dec 21, 2017 at 04:03:12PM -0600, Tom Lendacky wrote: > In preparation for encrypting more than just the kernel during early > boot processing, centralize the use of the PMD flag settings based > on the type of mapping desired. When 4KB aligned encryption is added, > this will allow

Re: [net-next] netfilter: add segment routing header 'srh' match

On Sun, 7 Jan 2018 00:40:03 +0100 Pablo Neira Ayuso wrote: > Hi Ahmed, > > On Fri, Dec 29, 2017 at 12:07:52PM +0100, Ahmed Abdelsalam wrote: > > It allows matching packets based on Segment Routing Header > > (SRH) information. > > The implementation considers revision 7 of the SRH draft. > >

Re: atm/clip: Use seq_puts() in svc_addr()

>> Is the function "seq_puts" a bit more efficient for the desired output >> of a single string in comparison to calling the function "seq_printf" >> for this purpose? > > Will you please be so kind and tell us? How do you think about to get the run time characteristics for these sequence output

Re: [PATCH] staging: iio: light: Add breaks to lengthy lines

On Sun, 2018-01-07 at 16:28 +, Jonathan Cameron wrote: > On Sun, 7 Jan 2018 15:08:01 + > George Edward Bulmer wrote: > > > This fixes three instances of checkpatch warning: > > WARNING: line over 80 characters > > > > Signed-off-by: George Edward Bulmer > > Applied, thanks, I

Aw: Re: dvb usb issues since kernel 4.9

Hi, here I provide lsusb from my affected hardware (technotrend s2-4600). http://ix.io/DLY With this hardware I had errors when recording with tvheadend. Livetv was ok, only channel switching made some problems sometimes. Please see attached tvheadend service logs. I also provide dmesg

[PATCH -next] ASoC: fsl_ssi: Fix build error

powerpc:mpc85xx_defconfig fails to build with the following errors. sound/soc/fsl/fsl_dma.c: In function 'fsl_soc_dma_probe': sound/soc/fsl/fsl_dma.c:916:34: error: 'CCSR_SSI_STX0' undeclared sound/soc/fsl/fsl_dma.c:917:34: error: 'CCSR_SSI_SRX0' undeclared Fixes: a818aa5f967b ("ASoC: fsl_ssi:

Re: [PATCH v2 2/8] x86/enter: MACROS to set/clear IBRS

On 01/07/2018 04:03 AM, Borislav Petkov wrote: > On Fri, Jan 05, 2018 at 06:12:17PM -0800, Tim Chen wrote: > >> Subject: Re: [PATCH v2 2/8] x86/enter: MACROS to set/clear IBRS > > Your subject needs to have a verb and not scream: > > Subject: [PATCH v2 2/8] x86/entry: Add macros to set/clear

Re: [PATCH v2 1/8] x86/feature: Detect the x86 IBRS feature to control Speculation

On 01/06/2018 04:56 AM, Borislav Petkov wrote: > On Fri, Jan 05, 2018 at 06:12:16PM -0800, Tim Chen wrote: > > <--- This needs an introductory sentence here. > >> cpuid ax=0x7, return rdx bit 26 to indicate presence of this feature > > You can write that as CPUID(7).RDX[26]. > >>

Re: [PATCH] staging: iio: light: Add breaks to lengthy lines

On Sun, 07 Jan 2018 08:42:27 -0800 Joe Perches wrote: > On Sun, 2018-01-07 at 16:28 +, Jonathan Cameron wrote: > > On Sun, 7 Jan 2018 15:08:01 + > > George Edward Bulmer wrote: > > > > > This fixes three instances of checkpatch warning: > > > WARNING: line over 80 characters > > >

<    1   2   3   4   5   6   7   8   9   >