Re: BUG: Bad page state (5)

/binfmt_elf.c:864 > > > > > search_binary_handler fs/exec.c:1656 [inline] > > > > > search_binary_handler+0x17f/0x570 fs/exec.c:1634 > > > > > exec_binprm fs/exec.c:1698 [inline] > > > > > __do_execve_file.isra.0+0x1394/0x23f0 fs

[tip:perf/core] perf, pt, coresight: Fix address filters for vmas with non-zero offset

Commit-ID: c60f83b813e5b25ccd5de7e8c8925c31b3aebcc1 Gitweb: https://git.kernel.org/tip/c60f83b813e5b25ccd5de7e8c8925c31b3aebcc1 Author: Alexander Shishkin AuthorDate: Fri, 15 Feb 2019 13:56:55 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 22 Feb 2019 16:52:07 -0300 perf,

[tip:perf/core] perf: Copy parent's address filter offsets on clone

Commit-ID: 18736eef12137c59f60cc9f56dc5bea05c92e0eb Gitweb: https://git.kernel.org/tip/18736eef12137c59f60cc9f56dc5bea05c92e0eb Author: Alexander Shishkin AuthorDate: Fri, 15 Feb 2019 13:56:54 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 22 Feb 2019 16:52:07 -0300 perf:

Re: [PATCH] cros_ec: instantiate properly Intel ISH MCU device

On Thu, Feb 28, 2019 at 12:05:35AM +0100, Enric Balletbo Serra wrote: > Missatge de Gwendal Grignou del dia dc., 27 de > febr. 2019 a les 19:37: > > On Wed, Feb 27, 2019 at 10:08 AM Enric Balletbo i Serra > > wrote: > > > On 27/2/19 16:13, Jett Rink wrote: > > You're right, the cros_ names are

Re: [PATCH 0/5] [v5] Allow persistent memory to be used like normal RAM

[ add Stephen and Juergen ] On Mon, Feb 25, 2019 at 11:02 AM Dave Hansen wrote: > > This is a relatively small delta from v4. The review comments seem > to be settling down, so it seems like we should start thinking about > how this might get merged. Are there any objections to taking it in >

Re: [PATCH] xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink

On Thu, Feb 28, 2019 at 03:18:59PM +0800, Yue Haibing wrote: > From: YueHaibing > > UBSAN report this: > > UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 > index 6 is out of range for type 'unsigned int [6]' > CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+

Re: [RFC PATCH 1/4] X.509: Parse public key parameters from x509 for akcipher

On Thu, Feb 28, 2019 at 10:04:49AM +0300, Vitaly Chikunov wrote: > > It seems that you insist on set_params to be removed and both key and > params to be passed into set_{pub,priv}_key. This means reworking all > existing RSA drivers and callers, right? Can you please confirm that > huge rework

Re: [PATCH V15 14/18] block: enable multipage bvecs

Hi Ming, On 2019-02-28 00:29, Ming Lei wrote: > On Wed, Feb 27, 2019 at 08:47:09PM +, Jon Hunter wrote: >> On 21/02/2019 08:42, Marek Szyprowski wrote: >>> On 2019-02-15 12:13, Ming Lei wrote: This patch pulls the trigger for multi-page bvecs. Reviewed-by: Omar Sandoval

[tip:perf/core] perf thread-stack: Hide x86 retpolines

Commit-ID: 3c0cd952cf051903929cd57b89034cc5f71f451d Gitweb: https://git.kernel.org/tip/3c0cd952cf051903929cd57b89034cc5f71f451d Author: Adrian Hunter AuthorDate: Wed, 9 Jan 2019 11:18:35 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 22 Feb 2019 16:49:49 -0300 perf

[tip:perf/core] perf thread-stack: Improve thread_stack__no_call_return()

Commit-ID: 1f35cd65386e02430546727bd3cc2508d052e3ec Gitweb: https://git.kernel.org/tip/1f35cd65386e02430546727bd3cc2508d052e3ec Author: Adrian Hunter AuthorDate: Wed, 9 Jan 2019 11:18:34 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 22 Feb 2019 11:42:34 -0300 perf

[tip:perf/core] perf annotate: Fix getting source line failure

Commit-ID: 11db1ad4513d6205d2519e1a30ff4cef746e3243 Gitweb: https://git.kernel.org/tip/11db1ad4513d6205d2519e1a30ff4cef746e3243 Author: Wei Li AuthorDate: Thu, 21 Feb 2019 17:57:16 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 21 Feb 2019 17:00:35 -0300 perf annotate: Fix

[tip:perf/core] perf tools: Make rm_rf() remove single file

Commit-ID: b4409ae112caa6315f6ee678e953b9fc93e6919c Gitweb: https://git.kernel.org/tip/b4409ae112caa6315f6ee678e953b9fc93e6919c Author: Jiri Olsa AuthorDate: Wed, 20 Feb 2019 13:28:00 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 20 Feb 2019 17:09:28 -0300 perf tools:

[tip:perf/core] perf cpumap: Increase debug level for cpu_map__snprint verbose output

Commit-ID: deb83da16c1f3412fcb33c8944b3d854c4b265d6 Gitweb: https://git.kernel.org/tip/deb83da16c1f3412fcb33c8944b3d854c4b265d6 Author: Jiri Olsa AuthorDate: Wed, 20 Feb 2019 13:27:59 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 20 Feb 2019 17:08:39 -0300 perf cpumap:

[tip:perf/core] perf bpf-event: Add missing new line into pr_debug call

Commit-ID: b20fe10642f90d17c07b5e621bf4c00093c5654b Gitweb: https://git.kernel.org/tip/b20fe10642f90d17c07b5e621bf4c00093c5654b Author: Jiri Olsa AuthorDate: Wed, 20 Feb 2019 13:27:58 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 20 Feb 2019 16:23:07 -0300 perf bpf-event:

[tip:perf/core] perf evsel: Force sample_type for slave events

Commit-ID: 6e7e8b9fec45f7bef11a5d9d2dd9febe439d4047 Gitweb: https://git.kernel.org/tip/6e7e8b9fec45f7bef11a5d9d2dd9febe439d4047 Author: Jiri Olsa AuthorDate: Wed, 20 Feb 2019 13:27:56 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 20 Feb 2019 16:08:59 -0300 perf evsel:

[tip:perf/core] perf script: Allow +- operator for type specific fields option

Commit-ID: 6ef362fd3cf3af5d8143a07b4ea20499bf2a9eec Gitweb: https://git.kernel.org/tip/6ef362fd3cf3af5d8143a07b4ea20499bf2a9eec Author: Jiri Olsa AuthorDate: Wed, 20 Feb 2019 13:27:57 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 20 Feb 2019 16:15:35 -0300 perf script:

[tip:perf/core] perf session: Don't report zero period samples for slave events

Commit-ID: 529c1a9e18c3b470d2eff7879923eda40b1431db Gitweb: https://git.kernel.org/tip/529c1a9e18c3b470d2eff7879923eda40b1431db Author: Jiri Olsa AuthorDate: Wed, 20 Feb 2019 13:27:55 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 20 Feb 2019 16:07:51 -0300 perf session:

[tip:perf/core] perf trace: Allow dumping a BPF map after setting up BPF events

Commit-ID: ff7a4f98d52cd3f13b1f4f6f22208498b0c113f7 Gitweb: https://git.kernel.org/tip/ff7a4f98d52cd3f13b1f4f6f22208498b0c113f7 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 19 Feb 2019 16:17:33 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 16:35:45 -0300

[tip:perf/core] perf bpf: Add bpf_map dumper

Commit-ID: d19f856479feef7c1383f02b87688563a0ef7a14 Gitweb: https://git.kernel.org/tip/d19f856479feef7c1383f02b87688563a0ef7a14 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 19 Feb 2019 16:11:56 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 16:11:56 -0300

[tip:perf/core] perf test: Fix failure of 'evsel-tp-sched' test on s390

Commit-ID: 03d309711d687460d1345de8a0363f45b1c8cd11 Gitweb: https://git.kernel.org/tip/03d309711d687460d1345de8a0363f45b1c8cd11 Author: Thomas Richter AuthorDate: Tue, 19 Feb 2019 16:36:39 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 13:43:29 -0300 perf test:

Re: [RFC v4 08/17] kunit: test: add support for test abort

On Tue, Feb 19, 2019 at 10:44 PM Frank Rowand wrote: > > On 2/19/19 7:39 PM, Brendan Higgins wrote: > > On Mon, Feb 18, 2019 at 11:52 AM Frank Rowand > > wrote: > >> > >> On 2/14/19 1:37 PM, Brendan Higgins wrote: > >>> Add support for aborting/bailing out of test cases. Needed for > >>>

[tip:perf/core] perf doc: Fix documentation of the Flags section in perf.data

Commit-ID: 8c23a522388b34cd7bc8473987eda0c75eb37c0e Gitweb: https://git.kernel.org/tip/8c23a522388b34cd7bc8473987eda0c75eb37c0e Author: Jonas Rabenstein AuthorDate: Tue, 19 Feb 2019 16:45:15 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 13:39:12 -0300 perf

[tip:perf/core] perf doc: Fix HEADER_CMDLINE description in perf.data documentation

Commit-ID: 7a663c0ff330a068c088ad46bb0130e651a9fec3 Gitweb: https://git.kernel.org/tip/7a663c0ff330a068c088ad46bb0130e651a9fec3 Author: Jonas Rabenstein AuthorDate: Tue, 19 Feb 2019 16:45:14 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 13:39:08 -0300 perf

[tip:perf/core] perf report: Don't shadow inlined symbol with different addr range

Commit-ID: 7346195e8643482968f547483e0d823ec1982fab Gitweb: https://git.kernel.org/tip/7346195e8643482968f547483e0d823ec1982fab Author: He Kuang AuthorDate: Tue, 19 Feb 2019 21:05:31 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 12:30:12 -0300 perf report:

[tip:perf/core] perf tools: Add numa_topology object

Commit-ID: 48e6c5acd36873ff022cd97de866bfd0a36a3b99 Gitweb: https://git.kernel.org/tip/48e6c5acd36873ff022cd97de866bfd0a36a3b99 Author: Jiri Olsa AuthorDate: Tue, 19 Feb 2019 10:58:14 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 12:21:06 -0300 perf tools: Add

[tip:perf/core] perf tools: Use sysfs__mountpoint() when reading cpu topology

Commit-ID: e19a01c1438e123d169fd09376a221d844797174 Gitweb: https://git.kernel.org/tip/e19a01c1438e123d169fd09376a221d844797174 Author: Jiri Olsa AuthorDate: Tue, 19 Feb 2019 10:58:15 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 12:21:10 -0300 perf tools: Use

[tip:perf/core] perf tools: Add cpu_topology object

Commit-ID: 5135d5efcbb439c2acb20d6197dd57af3a456e76 Gitweb: https://git.kernel.org/tip/5135d5efcbb439c2acb20d6197dd57af3a456e76 Author: Jiri Olsa AuthorDate: Tue, 19 Feb 2019 10:58:13 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 12:21:01 -0300 perf tools: Add

[tip:perf/core] perf tests shell: Skip trace+probe_vfs_getname.sh if built without trace support

Commit-ID: 83244772a4cf9490a54182be2f65f45d6b1a1ee8 Gitweb: https://git.kernel.org/tip/83244772a4cf9490a54182be2f65f45d6b1a1ee8 Author: Tommi Rantala AuthorDate: Fri, 15 Feb 2019 15:42:46 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 15 Feb 2019 13:42:26 -0300 perf tests

Re: [RFC PATCH] mm,memory_hotplug: Unlock 1GB-hugetlb on x86_64

On 27.02.19 23:00, Mike Kravetz wrote: > On 2/27/19 1:51 PM, Oscar Salvador wrote: >> On Thu, Feb 21, 2019 at 10:42:12AM +0100, Oscar Salvador wrote: >>> [1] https://lore.kernel.org/patchwork/patch/998796/ >>> >>> Signed-off-by: Oscar Salvador >> >> Any further comments on this? >> I do have a

[tip:perf/core] perf header: Fix wrong node write in NUMA_TOPOLOGY feature

Commit-ID: b00ccb27f97367d89e2d7b419ed198b0985be55d Gitweb: https://git.kernel.org/tip/b00ccb27f97367d89e2d7b419ed198b0985be55d Author: Jiri Olsa AuthorDate: Tue, 19 Feb 2019 10:58:12 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 19 Feb 2019 12:20:55 -0300 perf header:

Re: [PATCH RESEND net] net: phy: xgmiitorgmii: Support generic PHY status read

Hi, On Wed, Feb 27, 2019 at 2:35 PM Harini Katakam wrote: > > Hi Andrew, Paul, > > On Wed, Feb 27, 2019 at 2:15 PM Michal Simek wrote: > > > > On 21. 02. 19 12:03, Michal Simek wrote: > > > On 21. 02. 19 11:24, Paul Kocialkowski wrote: > > >> Hi, > > >> > > >> On Wed, 2019-02-20 at 07:58 +0100,

Re: [GIT PULL] perf/core improvements and fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, this is on top of my previous pull > request, perf-core-for-mingo-5.1-20190220. > > - Arnaldo > > Test results at the end of this message, as usual. > > The following changes since commit

Re: [GIT PULL 00/17] perf/core improvements and fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, > > - Arnaldo > > Test results at the end of this message, as usual. > > The following changes since commit 43f4e6279f05eefac058a3524e184cecae463bfe: > > Merge tag 'perf-core-for-mingo-5.1-20190214' of >

Re: [bug report][stable] perf probe: failed to add events

On 28/02/19 4:07 AM, Joseph Qi wrote: > Hi Adrian, > > On 19/2/27 20:39, Adrian Hunter wrote: >> Seems to be fixed by this: >> >> From: Adrian Hunter >> Date: Wed, 27 Feb 2019 05:35:25 +0200 >> Subject: [PATCH] perf probe: Fix getting the kernel map >> >> Since commit 4d99e4136580 ("perf

[PATCH] xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink

From: YueHaibing UBSAN report this: UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS

[tip:locking/core] lockdep/lib/tests: Fix run_tests.sh

Commit-ID: d93ac78bf7b37db36fa00225f8e9a14c7ed1b2ba Gitweb: https://git.kernel.org/tip/d93ac78bf7b37db36fa00225f8e9a14c7ed1b2ba Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:57 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:48 +0100 lockdep/lib/tests: Fix

[tip:locking/core] lockdep/lib/tests: Test dynamic key registration

Commit-ID: f214737b75b0ee79763b5c058b9d5e83d711348d Gitweb: https://git.kernel.org/tip/f214737b75b0ee79763b5c058b9d5e83d711348d Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:58 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:48 +0100 lockdep/lib/tests:

Re: [PATCH v3] xfrm: policy: Fix possible user after free in __xfrm_policy_unlink

Pls ignore this, will fix the patch title On 2019/2/28 14:56, Yue Haibing wrote: > From: YueHaibing > > UBSAN report this: > > UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 > index 6 is out of range for type 'unsigned int [6]' > CPU: 1 PID: 0 Comm: swapper/1 Not tainted

[tip:locking/core] kernel/workqueue: Use dynamic lockdep keys for workqueues

Commit-ID: 669de8bda87b92ab9a2fc663b3f5743c2ad1ae9f Gitweb: https://git.kernel.org/tip/669de8bda87b92ab9a2fc663b3f5743c2ad1ae9f Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:54 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:47 +0100 kernel/workqueue: Use

RE: [RFC PATCH] soc/fsl/qe: support MPC8309

On Tue, Feb 26, 2019 at 2:49 AM Rasmus Villemoes wrote: > -Original Message- > From: Rasmus Villemoes > Sent: 2019年2月26日 16:48 > To: Qiang Zhao ; Leo Li > Cc: linux-kernel@vger.kernel.org; Valentin Longchamp > ; Scott Wood ; > Rasmus Villemoes > Subject: [RFC PATCH] soc/fsl/qe:

[tip:locking/core] locking/lockdep: Add support for dynamic keys

Commit-ID: 108c14858b9ea224686e476c8f5ec345a0df9e27 Gitweb: https://git.kernel.org/tip/108c14858b9ea224686e476c8f5ec345a0df9e27 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:53 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:47 +0100 locking/lockdep: Add

[tip:locking/core] locking/lockdep: Verify whether lock objects are small enough to be used as class keys

Commit-ID: 4bf508621855613ca2ac782f70c3171e0e8bb011 Gitweb: https://git.kernel.org/tip/4bf508621855613ca2ac782f70c3171e0e8bb011 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:52 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:46 +0100 locking/lockdep:

[tip:locking/core] locking/lockdep: Check data structure consistency

Commit-ID: b526b2e39a53b312f5a6867ce57824247aa0ce8b Gitweb: https://git.kernel.org/tip/b526b2e39a53b312f5a6867ce57824247aa0ce8b Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:51 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:45 +0100 locking/lockdep: Check

[PATCH v12 3/4] pstore/blk: support pmsg for pstore block

To enable pmsg, just set pmsg_size when block device register blkzone. Signed-off-by: liaoweixiong --- fs/pstore/Kconfig | 21 fs/pstore/blkoops.c| 10 ++ fs/pstore/blkzone.c| 253 + include/linux/pstore_blk.h | 1 +

[PATCH v12 4/4] Documentation: pstore/blk: create document for pstore_blk

The document, at Documentation/admin-guide/pstore-block.rst, tells user how to use pstore_blk and the attentions about panic read/write Signed-off-by: liaoweixiong --- Documentation/admin-guide/pstore-block.rst | 233 + MAINTAINERS|

[PATCH v12 2/4] pstore/blk: add blkoops for pstore_blk

blkoops is a sample for pstore/blk. It can only record oops, excluding panics as no read/write apis for panic registered. It support settings on Kconfg/module parameters. It can record oops log even power failure if "PSTORE_BLKOOPS_BLKDEV" on Kconfig or "blkdev" on module parameter is valid.

Re: [PATCH net-next] switchdev: Remove unused transaction item queue

Thu, Feb 28, 2019 at 01:29:16AM CET, f.faine...@gmail.com wrote: >There are no more in tree users of the >switchdev_trans_item_{dequeue,enqueue} or switchdev_trans_item structure >in the kernel since commit 00fc0c51e35b ("rocker: Change world_ops API >and implementation to be switchdev

[PATCH v12 1/4] pstore/blk: new support logger for block devices

pstore_blk is similar to pstore_ram, but dump log to block devices rather than persistent ram. Why should we need pstore_blk? 1. Most embedded intelligent equipment have no persistent ram, which increases costs. We perfer to cheaper solutions, like block devices. In fact, there is already a

Re: [RFC PATCH 1/4] X.509: Parse public key parameters from x509 for akcipher

On Thu, Feb 28, 2019 at 10:04:49AM +0300, Vitaly Chikunov wrote: > Herbert, > > On Thu, Feb 28, 2019 at 02:14:44PM +0800, Herbert Xu wrote: > > On Sun, Feb 24, 2019 at 09:48:40AM +0300, Vitaly Chikunov wrote: > > > > > > If we pass SubjectPublicKeyInfo into set_pub_key itself (making > > >

[PATCH v12 0/4] pstore/block: new support logger for block devices

Why should we need pstore_block? 1. Most embedded intelligent equipment have no persistent ram, which increases costs. We perfer to cheaper solutions, like block devices. In fast, there is already a sample for block device logger in driver MTD (drivers/mtd/mtdoops.c). 2. Do not any equipment have

[tip:locking/core] locking/lockdep: Reuse lock chains that have been freed

Commit-ID: de4643a77356a77bce73f64275b125b4b71a69cf Gitweb: https://git.kernel.org/tip/de4643a77356a77bce73f64275b125b4b71a69cf Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:50 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:45 +0100 locking/lockdep: Reuse

[tip:locking/core] locking/lockdep: Fix a comment in add_chain_cache()

Commit-ID: 527af3ea273b2cf0c017a2c90090b3c94af8aba4 Gitweb: https://git.kernel.org/tip/527af3ea273b2cf0c017a2c90090b3c94af8aba4 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:49 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:45 +0100 locking/lockdep: Fix a

[tip:locking/core] locking/lockdep: Introduce lockdep_next_lockchain() and lock_chain_count()

Commit-ID: 2212684adff79e2704a2792ff46682afb9246fc8 Gitweb: https://git.kernel.org/tip/2212684adff79e2704a2792ff46682afb9246fc8 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:48 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:44 +0100 locking/lockdep:

Re: [PATCH] xhci: use iopoll for xhci_handshake

On Wed, Feb 27, 2019 at 03:19:17PM -0700, Daniel Kurtz wrote: > In cases such as xhci_abort_cmd_ring(), xhci_handshake() is called with > a spin lock held (and local interrupts disabled) with a huge 5 second > timeout. This can translates to 5 million calls to udelay(1). By its > very nature,

[tip:locking/core] locking/lockdep: Reuse list entries that are no longer in use

Commit-ID: ace35a7ac493d4284a57ad807579011bebba891c Gitweb: https://git.kernel.org/tip/ace35a7ac493d4284a57ad807579011bebba891c Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:47 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:44 +0100 locking/lockdep: Reuse

[tip:locking/core] locking/lockdep: Free lock classes that are no longer in use

Commit-ID: a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 Gitweb: https://git.kernel.org/tip/a0b0fd53e1e67639b303b15939b9c653dbe7a8c4 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:46 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:43 +0100 locking/lockdep: Free

[tip:locking/core] locking/lockdep: Update two outdated comments

Commit-ID: 29fc33fb7283970701355dc89badba4ed21c7092 Gitweb: https://git.kernel.org/tip/29fc33fb7283970701355dc89badba4ed21c7092 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:45 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:43 +0100 locking/lockdep:

[tip:locking/core] locking/lockdep: Make it easy to detect whether or not inside a selftest

Commit-ID: cdc84d794947b5431c0a6916c303aee7114819d2 Gitweb: https://git.kernel.org/tip/cdc84d794947b5431c0a6916c303aee7114819d2 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:44 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:43 +0100 locking/lockdep: Make

[tip:locking/core] locking/lockdep: Split lockdep_free_key_range() and lockdep_reset_lock()

Commit-ID: 956f3563a8387beb7758f2e8ee483639ef91afc6 Gitweb: https://git.kernel.org/tip/956f3563a8387beb7758f2e8ee483639ef91afc6 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:43 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:42 +0100 locking/lockdep: Split

[tip:locking/core] locking/lockdep: Make zap_class() remove all matching lock order entries

Commit-ID: 86cffb80a525f7b8f969c8c79669d383e02f17d1 Gitweb: https://git.kernel.org/tip/86cffb80a525f7b8f969c8c79669d383e02f17d1 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:41 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:40 +0100 locking/lockdep: Make

[tip:locking/core] locking/lockdep: Initialize the locks_before and locks_after lists earlier

Commit-ID: feb0a3865ed2f7d66a1f2686f7ad784422c249ad Gitweb: https://git.kernel.org/tip/feb0a3865ed2f7d66a1f2686f7ad784422c249ad Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:42 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:41 +0100 locking/lockdep:

[tip:locking/core] locking/lockdep: Reorder struct lock_class members

Commit-ID: 09329d1c2024522308ca4de977fc6bba753bab1a Gitweb: https://git.kernel.org/tip/09329d1c2024522308ca4de977fc6bba753bab1a Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:40 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:40 +0100 locking/lockdep:

Re: [RFC PATCH 1/4] X.509: Parse public key parameters from x509 for akcipher

Herbert, On Thu, Feb 28, 2019 at 02:14:44PM +0800, Herbert Xu wrote: > On Sun, Feb 24, 2019 at 09:48:40AM +0300, Vitaly Chikunov wrote: > > > > If we pass SubjectPublicKeyInfo into set_pub_key itself (making > > set_params not needed) we will break ABI and compatibility with RSA > > drivers,

Re: [PATCH v10 0/9] support ROHM BD70528 PMIC

Hello Lee and Mark, On Thu, Feb 14, 2019 at 03:02:37PM +0200, Matti Vaittinen wrote: > Patch series introducing support for ROHM BD70528 PMIC > > ROHM BD70528 is a programmable Power Management IC for battery > powered 'ultra low power' systems like the pre-announced NXP > i.MX7 ULP. This patch

[tip:locking/core] locking/lockdep: Avoid that add_chain_cache() adds an invalid chain to the cache

Commit-ID: 523b113bace5e64e860d8c61d7aa25057d274753 Gitweb: https://git.kernel.org/tip/523b113bace5e64e860d8c61d7aa25057d274753 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:39 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:40 +0100 locking/lockdep: Avoid

[tip:locking/core] locking/lockdep: Fix reported required memory size (2/2)

Commit-ID: 15ea86b58c71d05e0921bebcf707aa30e43e9e25 Gitweb: https://git.kernel.org/tip/15ea86b58c71d05e0921bebcf707aa30e43e9e25 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:38 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:39 +0100 locking/lockdep: Fix

[tip:locking/core] locking/lockdep: Fix reported required memory size (1/2)

Commit-ID: 7ff8517e1034f26dde03d6df4026f085480408f0 Gitweb: https://git.kernel.org/tip/7ff8517e1034f26dde03d6df4026f085480408f0 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:37 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:39 +0100 locking/lockdep: Fix

Re: linux-next: manual merge of the staging tree with the net-next tree

On Thu, Feb 28, 2019 at 03:52:01PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the staging tree got a conflict in: > > drivers/staging/fsl-dpaa2/ethsw/ethsw.c > > between commit: > > 570b68c8ddde ("staging: fsl-dpaa2: ethsw: Handle SWITCHDEV_PORT_ATTR_SET") >

[tip:locking/core] locking/lockdep: Fix two 32-bit compiler warnings

Commit-ID: 09d75ecb122d8b600d76e3b8d53a10ffbe3bcec2 Gitweb: https://git.kernel.org/tip/09d75ecb122d8b600d76e3b8d53a10ffbe3bcec2 Author: Bart Van Assche AuthorDate: Thu, 14 Feb 2019 15:00:36 -0800 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:38 +0100 locking/lockdep: Fix

[RFC PATCH 2/2] spi: spi-mem: Add support for Zynq QSPI controller

Add support for QSPI controller driver used by Xilinx Zynq SOC. Signed-off-by: Naga Sureshkumar Relli --- drivers/spi/Kconfig | 8 + drivers/spi/Makefile| 1 + drivers/spi/spi-zynq-qspi.c | 780 3 files changed, 789 insertions(+)

[RFC PATCH 0/2] RFC for Zynq QSPI controller driver

Xilinx Zynq uses a QSPI controller that implements all the functionality required to support Quad SPI NOR flash devices. This driver along with the SPI MEM and MTD layer is used to support flash devices. The flash device(s) can be connected in three configurations to this controller: 1. Single -

[tip:locking/core] locking/qspinlock: Remove unnecessary BUG_ON() call

Commit-ID: 733000c7ffd9d9c8c4fdfd82f0d41956c8cf0537 Gitweb: https://git.kernel.org/tip/733000c7ffd9d9c8c4fdfd82f0d41956c8cf0537 Author: Waiman Long AuthorDate: Sun, 24 Feb 2019 20:14:13 -0500 Committer: Ingo Molnar CommitDate: Thu, 28 Feb 2019 07:55:38 +0100 locking/qspinlock: Remove

[RFC PATCH 1/2] dt-bindings: spi: Add device tree binding documentation for Zynq QSPI controller

This patch adds the dts binding document for Zynq SOC QSPI controller. Signed-off-by: Naga Sureshkumar Relli --- .../devicetree/bindings/spi/spi-zynq-qspi.txt | 25 ++ 1 file changed, 25 insertions(+) create mode 100644

Re: [PATCH v3 5/5] tracing/probe: Support user-space dereference

Hi Steve, Thank you for the review. On Wed, 27 Feb 2019 21:31:32 -0500 Steven Rostedt wrote: > On Wed, 27 Feb 2019 23:44:42 +0900 > Masami Hiramatsu wrote: > > > > > +.. _user_mem_access: > > +User Memory Access > > +-- > > +Kprobe events supports user-space memory access.

[PATCH 2/2] can: flexcan: add ISO CAN FD feature support

ISO CAN FD is introduced to increase the failture detection capability than non-ISO CAN FD. The non-ISO CAN FD is still supported by FlexCAN so that it can be used mainly during an intermediate phase, for evaluation and development purposes. Therefore, it is strongly recommended to configure

[PATCH 1/2] can: flexcan: add CANFD BRS support and improve bittiming setting

From: Dong Aisheng This patch intends to add CANFD BitRate Switch(BRS) support. Bit timing must be set in CBT register other than CTRL1 register when CANFD supports BRS, it will extend the range of all CAN bit timing variables (PRESDIV, PROPSEG, PSEG1, PSEG2 and RJW), which will improve the bit

[PATCH v3] xfrm: policy: Fix possible user after free in __xfrm_policy_unlink

From: YueHaibing UBSAN report this: UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS

[PATCH 0/2] can: flexcan: add CANFD BRS and ISO FD support

Hi Marc, This patch set intends to enable CANFD bitrate switch and ISO FD mode support. You may need to firstly review the patch set([PATCH 0/3] can: flexcan: add imx8qm support). I noticed that you have been reviewing my patches recetnly, please feel free to let me know if you want me to

Re: BUG: Bad page state (5)

mmon fs/exec.c:1865 [inline] > > > > do_execve fs/exec.c:1882 [inline] > > > > __do_sys_execve fs/exec.c:1958 [inline] > > > > __se_sys_execve fs/exec.c:1953 [inline] > > > > __x64_sys_execve+0x8f/0xc0 fs/exec.c:1953 > > > > do_sy

Re: kernel panic: MAC Initialization failed.

On Wed, Feb 27, 2019 at 11:37 PM Tetsuo Handa wrote: > > On 2019/02/28 2:02, syzbot wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:7b827ff9af88 Add linux-next specific files for 20190227 > > git tree:

Re: [RFC] kprobes: Fix locking in recycle_rp_inst

On Wed, 27 Feb 2019 14:33:09 +0100 Jiri Olsa wrote: > On Wed, Feb 27, 2019 at 05:38:46PM +0900, Masami Hiramatsu wrote: > > SNIP > > > > When we switch it to raw_spin_lock_irqsave the return probe > > > on _raw_spin_lock starts working. > > > > Yes, there can be a race between probes and

Re: [RFC PATCH v1 07/13] devicetree: bindings: Document first ROHM BD70528 bindings

Hello Rob, All Sorry for long delay - I was ill for a few days. Back at the business now =) Rob, maybe dropping the RFC tag has messed your book keeping? This is the latest version:

Re: [PATCH v2] xfrm: policy: Fix possible user after free in __xfrm_policy_unlink

On 2019/2/28 14:41, Herbert Xu wrote: > On Thu, Feb 28, 2019 at 02:38:01PM +0800, Yue Haibing wrote: >> >> diff --git a/net/xfrm/xfrm_user.c b/net/xfrm/xfrm_user.c >> index a131f9f..aaa45c9 100644 >> --- a/net/xfrm/xfrm_user.c >> +++ b/net/xfrm/xfrm_user.c >> @@ -1424,7 +1424,8 @@ static int

[PATCH v2] dts: arm64: add CoreSight trace support for hi3660

This patch adds devicetree entries for the CoreSight trace components on hi3660. Signed-off-by: Wanglai Shi --- .../arm64/boot/dts/hisilicon/hi3660-coresight.dtsi | 429 + arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 2 + 2 files changed, 431 insertions(+) create

Re: [PATCH V7 1/2] arm64: dts: freescale: imx8qxp: add cpu opp table

On Thu, Feb 28, 2019 at 06:18:30AM +, Anson Huang wrote: > Hi, Shawn > > Best Regards! > Anson Huang > > > -Original Message- > > From: Shawn Guo [mailto:shawn...@kernel.org] > > Sent: 2019年2月28日 11:19 > > To: Anson Huang > > Cc: robh...@kernel.org; mark.rutl...@arm.com;

Re: [PATCH v6 1/6] arm64/kvm: preserve host HCR_EL2 value

Hi, On 2/21/19 5:20 PM, Mark Rutland wrote: Hi, On Tue, Feb 19, 2019 at 02:54:26PM +0530, Amit Daniel Kachhap wrote: From: Mark Rutland When restoring HCR_EL2 for the host, KVM uses HCR_HOST_VHE_FLAGS, which is a constant value. This works today, as the host HCR_EL2 value is always the

Re: [PATCH v2] PCI: pciehp: Report degraded links via link bandwidth notification

On Wed, Feb 27, 2019 at 08:21:58PM +, alex_gagn...@dellteam.com wrote: > On 2/24/19 8:29 PM, Lukas Wunner wrote: > > On Fri, Dec 07, 2018 at 12:20:00PM -0600, Alexandru Gagniuc wrote: > > > Q: Why is this unconditionally compiled in? > > > A: The symmetrical check in pci probe() is also always

Re: [PATCH v2] xfrm: policy: Fix possible user after free in __xfrm_policy_unlink

On Thu, Feb 28, 2019 at 02:38:01PM +0800, Yue Haibing wrote: > > diff --git a/net/xfrm/xfrm_user.c b/net/xfrm/xfrm_user.c > index a131f9f..aaa45c9 100644 > --- a/net/xfrm/xfrm_user.c > +++ b/net/xfrm/xfrm_user.c > @@ -1424,7 +1424,8 @@ static int verify_newpolicy_info(struct >

kernel panic: MAC Initialization failed. (2)

Hello, syzbot found the following crash on: HEAD commit:7b827ff9af88 Add linux-next specific files for 20190227 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=10f71894c0 kernel config: https://syzkaller.appspot.com/x/.config?x=5fa6b8975759dcc5

Re: [PATCH] drm/vkms: fix use-after-free when drm_gem_handle_create() fails

On Thu, Feb 28, 2019 at 12:12 AM Rodrigo Siqueira wrote: > > On 02/26, Eric Biggers wrote: > > From: Eric Biggers > > > > If drm_gem_handle_create() fails in vkms_gem_create(), then the > > vkms_gem_object is freed twice: once when the reference is dropped by > > drm_gem_object_put_unlocked(),

Re: [RFC v9 5/5] Documentation: pstore/blk: create document for pstore_blk

Thank you for your correction. I will update the patch in the 12th version. On 2019/02/28 13:15, Randy Dunlap wrote: > On 2/19/19 3:52 AM, liaoweixiong wrote: >> The document, at Documentation/admin-guide/pstore-block.rst, >> tells user how to use pstore_blk and the attentions about panic >>

Re: [PATCH 08/12] crypto: add missing of_node_put after of_device_is_available

On Sat, Feb 23, 2019 at 02:20:39PM +0100, Julia Lawall wrote: > Add an of_node_put when a tested device node is not available. > > The semantic patch that fixes this problem is as follows > (http://coccinelle.lip6.fr): > > // > @@ > identifier f; > local idexpression e; > expression x; > @@ >

[PATCH] perf util: Refactor time range parsing code

Jiri points out that we don't need any time checking and time string parsing if the --time option is not set. That makes sense. This patch refactors the time range parsing code, move the duplicated code from perf report and perf script to time_utils and check if --time option is set before

[PATCH v2] xfrm: policy: Fix possible user after free in __xfrm_policy_unlink

From: YueHaibing UBSAN report this: UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS

Re: [PATCH v4 0/3] add AES support for Exynos5433

On Fri, Feb 22, 2019 at 01:21:41PM +0100, Kamil Konieczny wrote: > Add slimSSS node to DT and crypto AES support for Exynos5433. Tested on > Exynos5433 board with crypto run-time self tests and with tcrypt with > command insmod tcrypt.ko mode=500 sec=1 > > Changes since v3: > - moved bindings

Re: [PATCH v3] PCI: portdrv: Report degraded links via link bandwidth notification

On Wed, Feb 27, 2019 at 02:58:17PM -0600, Alexandru Gagniuc wrote: > A warning is generated when a PCIe device is probed with a degraded > link, but there was no similar mechanism to warn when the link becomes > degraded after probing. The Link Bandwidth Notification provides this > mechanism. >

Re: [PATCH v2] crypto: s5p: update iv after AES-CBC op end

On Tue, Feb 19, 2019 at 05:02:32PM +0100, Kamil Konieczny wrote: > Fix bug "s5p-sss crypto driver doesn't set next AES-CBC IV". While at this, > fix also AES-CTR mode. Tested on Odroid U3 with Eric Biggers branch > "iv-out-testing". > > Signed-off-by: Kamil Konieczny > Reported-by: Eric Biggers

Re: [PATCH] crypto: af_alg - use struct_size() in sock_kfree_s()

On Thu, Feb 21, 2019 at 12:04:23PM -0600, Gustavo A. R. Silva wrote: > Make use of the struct_size() helper instead of an open-coded version > in order to avoid any potential type mistakes, in particular in the > context in which this code is being used. > > So, change the following form: > >

Re: [PATCH] crypto: s5p-sss - Use AES_BLOCK_SIZE define instead of number

On Tue, Feb 19, 2019 at 01:01:03PM +0100, Krzysztof Kozlowski wrote: > Replace hard coded AES block size with define. > > Signed-off-by: Krzysztof Kozlowski > --- > drivers/crypto/s5p-sss.c | 6 -- > 1 file changed, 4 insertions(+), 2 deletions(-) Patch applied. Thanks. -- Email: Herbert

Re: [PATCH] hwrng: bcm2835 - fix probe as platform device

On Tue, Feb 19, 2019 at 01:16:08PM +0100, Jonas Gorski wrote: > BCM63XX (MIPS) does not use device tree, so there cannot be any > of_device_id, causing the driver to fail on probe: > > [0.904564] bcm2835-rng: probe of bcm63xx-rng failed with error -22 > > Fix this by checking for match data

  1   2   3   4   5   6   7   8   9   >