[PATCH v2 3/4] lockdep: Move data of CONFIG_LOCKDEP_PAGELOCK from page to page_ext

CONFIG_LOCKDEP_PAGELOCK needs to keep lockdep_map_cross per page. Since it's a debug feature, it's preferred to keep it in struct page_ext rather than struct page. Move it to struct page_ext. Signed-off-by: Byungchul Park --- include/linux/mm_types.h | 4 ---

[PATCH v2 3/4] lockdep: Move data of CONFIG_LOCKDEP_PAGELOCK from page to page_ext

CONFIG_LOCKDEP_PAGELOCK needs to keep lockdep_map_cross per page. Since it's a debug feature, it's preferred to keep it in struct page_ext rather than struct page. Move it to struct page_ext. Signed-off-by: Byungchul Park --- include/linux/mm_types.h | 4 --- include/linux/page-flags.h | 19

[PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

For now, wait_for_completion() / complete() works with lockdep, add lock_page() / unlock_page() and its family to lockdep support. Changes from v1 - Move lockdep_map_cross outside of page_ext to make it flexible - Prevent allocating lockdep_map per page by default - Add a boot parameter

[PATCH v2 2/4] lockdep: Apply lock_acquire(release) on __Set(__Clear)PageLocked

Usually PG_locked bit is updated by lock_page() or unlock_page(). However, it can be also updated through __SetPageLocked() or __ClearPageLockded(). They have to be considered, to get paired between acquire and release. Furthermore, e.g. __SetPageLocked() in add_to_page_cache_lru() is called

[PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

For now, wait_for_completion() / complete() works with lockdep, add lock_page() / unlock_page() and its family to lockdep support. Changes from v1 - Move lockdep_map_cross outside of page_ext to make it flexible - Prevent allocating lockdep_map per page by default - Add a boot parameter

[PATCH v2 2/4] lockdep: Apply lock_acquire(release) on __Set(__Clear)PageLocked

Usually PG_locked bit is updated by lock_page() or unlock_page(). However, it can be also updated through __SetPageLocked() or __ClearPageLockded(). They have to be considered, to get paired between acquire and release. Furthermore, e.g. __SetPageLocked() in add_to_page_cache_lru() is called

Re: [PATCH] cgroup/cpuset: fix circular locking dependency

On 11/28/2017 05:05 PM, Prateek Sood wrote: > CPU1 > cpus_read_lock+0x3e/0x80 > static_key_slow_inc+0xe/0xa0 > cpuset_css_online+0x62/0x330 > online_css+0x26/0x80 > cgroup_apply_control_enable+0x266/0x3d0 > cgroup_mkdir+0x37d/0x4f0 > kernfs_iop_mkdir+0x53/0x80 > vfs_mkdir+0x10e/0x1a0 >

Re: [PATCH] cgroup/cpuset: fix circular locking dependency

On 11/28/2017 05:05 PM, Prateek Sood wrote: > CPU1 > cpus_read_lock+0x3e/0x80 > static_key_slow_inc+0xe/0xa0 > cpuset_css_online+0x62/0x330 > online_css+0x26/0x80 > cgroup_apply_control_enable+0x266/0x3d0 > cgroup_mkdir+0x37d/0x4f0 > kernfs_iop_mkdir+0x53/0x80 > vfs_mkdir+0x10e/0x1a0 >

Re: [PATCH 1/1] timecounter: Make cyclecounter struct part of timecounter struct

On 12/2/2017 11:34 PM, Richard Cochran wrote: On Sat, Dec 02, 2017 at 10:01:35AM +0530, Sagar Arun Kamble wrote: There is no real need for the users of timecounters to define cyclecounter and timecounter variables separately. Since timecounter will always be based on cyclecounter, have

Re: [PATCH 1/1] timecounter: Make cyclecounter struct part of timecounter struct

On 12/2/2017 11:34 PM, Richard Cochran wrote: On Sat, Dec 02, 2017 at 10:01:35AM +0530, Sagar Arun Kamble wrote: There is no real need for the users of timecounters to define cyclecounter and timecounter variables separately. Since timecounter will always be based on cyclecounter, have

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Mon, Dec 4, 2017 at 10:25 AM, Tobin C. Harding wrote: > > > With the 'eval', no warning, it's fine. > > Why not use hex()? > > > > foreach my $config_file (@config_files) { > > + $config_file =~ s/\R*//g; > > Is there some reason you don't use chomp()?

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Mon, Dec 4, 2017 at 10:25 AM, Tobin C. Harding wrote: > > > With the 'eval', no warning, it's fine. > > Why not use hex()? > > > > foreach my $config_file (@config_files) { > > + $config_file =~ s/\R*//g; > > Is there some reason you don't use chomp()? Tobin, now you

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Mon, Dec 04, 2017 at 10:11:21AM +0530, kaiwan.billimo...@gmail.com wrote: > On Mon, 2017-12-04 at 11:11 +1100, Tobin C. Harding wrote: > > On Fri, Dec 01, 2017 at 06:39:07PM +0530, kaiwan.billimo...@gmail.com wrote: > > > > @@ -267,7 +266,7 @@ sub is_false_positive > > > sub

Re: [PATCH v2 00/15] NTB: Add full multi-port API support to the test drivers

On 03/12/17 12:17 PM, Serge Semin wrote: > The multi-port NTB API was introduced in kernel 4.13 as well as the > first driver for the true multi-port devices of IDT PCIe-switches > series. But the test drivers still were left almost unchanged. Yes, > they didn't fail being used with new NTB API,

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Mon, Dec 04, 2017 at 10:11:21AM +0530, kaiwan.billimo...@gmail.com wrote: > On Mon, 2017-12-04 at 11:11 +1100, Tobin C. Harding wrote: > > On Fri, Dec 01, 2017 at 06:39:07PM +0530, kaiwan.billimo...@gmail.com wrote: > > > > @@ -267,7 +266,7 @@ sub is_false_positive > > > sub

Re: [PATCH v2 00/15] NTB: Add full multi-port API support to the test drivers

On 03/12/17 12:17 PM, Serge Semin wrote: > The multi-port NTB API was introduced in kernel 4.13 as well as the > first driver for the true multi-port devices of IDT PCIe-switches > series. But the test drivers still were left almost unchanged. Yes, > they didn't fail being used with new NTB API,

Re: [PATCH net-next] bridge: ebtables: Avoid resetting limit rule state

Hi Pablo, Thanks for your reply! On Tue, Nov 28, 2017 at 12:30:08AM +0100, Pablo Neira Ayuso wrote: > [...] > > diff --git a/net/bridge/netfilter/ebt_limit.c > > b/net/bridge/netfilter/ebt_limit.c > > index 61a9f1be1263..f74b48633feb 100644 > > --- a/net/bridge/netfilter/ebt_limit.c > > +++

Re: [PATCH net-next] bridge: ebtables: Avoid resetting limit rule state

Hi Pablo, Thanks for your reply! On Tue, Nov 28, 2017 at 12:30:08AM +0100, Pablo Neira Ayuso wrote: > [...] > > diff --git a/net/bridge/netfilter/ebt_limit.c > > b/net/bridge/netfilter/ebt_limit.c > > index 61a9f1be1263..f74b48633feb 100644 > > --- a/net/bridge/netfilter/ebt_limit.c > > +++

[PATCH v2 2/2] arm64: allwinner: a64-sopine: Fix to use dcdc1 regulator instead of vcc3v3

Since current tree support AXP803 regulators, replace fixed regulator vcc3v3 with AXP803 dcdc1 regulator where ever it need to replace. Tested mmc0 on sopine baseboard. Signed-off-by: Jagan Teki --- Changes for v2: - Commit message edited as fix since it has issue

Re: KASAN: slab-out-of-bounds Read in strcmp

On Sun, Dec 3, 2017 at 2:27 PM, Tetsuo Handa wrote: > Tetsuo Handa wrote: >> which will allow strcmp() to trigger out of bound read when "size" is >> larger than strlen(initial_sid_to_string[i]). > > Oops. "smaller" than. > >> >> Thus, I guess the simplest fix

[PATCH v2 2/2] arm64: allwinner: a64-sopine: Fix to use dcdc1 regulator instead of vcc3v3

Since current tree support AXP803 regulators, replace fixed regulator vcc3v3 with AXP803 dcdc1 regulator where ever it need to replace. Tested mmc0 on sopine baseboard. Signed-off-by: Jagan Teki --- Changes for v2: - Commit message edited as fix since it has issue with sdcard detect.

Re: KASAN: slab-out-of-bounds Read in strcmp

On Sun, Dec 3, 2017 at 2:27 PM, Tetsuo Handa wrote: > Tetsuo Handa wrote: >> which will allow strcmp() to trigger out of bound read when "size" is >> larger than strlen(initial_sid_to_string[i]). > > Oops. "smaller" than. > >> >> Thus, I guess the simplest fix is to use strncmp() instead of

[PATCH v2 1/2] arm64: dts: a64-olinuxino: Enable RTL8723BS WiFi

Enable RTL8723BS WiFi chip on a64-olinuxino board: - WiFi SDIO interface is connected to MMC1 - WiFi REG_ON pin connected to gpio PL2: attach to mmc-pwrseq - WiFi HOST_WAKE pin connected to gpio PL3 Signed-off-by: Jagan Teki Acked-by: Maxime Ripard

[PATCH v2 1/2] arm64: dts: a64-olinuxino: Enable RTL8723BS WiFi

Enable RTL8723BS WiFi chip on a64-olinuxino board: - WiFi SDIO interface is connected to MMC1 - WiFi REG_ON pin connected to gpio PL2: attach to mmc-pwrseq - WiFi HOST_WAKE pin connected to gpio PL3 Signed-off-by: Jagan Teki Acked-by: Maxime Ripard --- Changes for v2: - Remove wrong commit

Re: [PATCH] fsi: Add Self Boot Engine FIFO FSI client

Hi Andrew, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] fsi: Add Self Boot Engine FIFO FSI client

Hi Andrew, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

RE: [PATCH] Support TrackStick of Thinkpad L570

Hi, Pali, I don't get your point. Please modify the code if you have an idea. Best Regards, Masaki Ota -Original Message- From: Pali Rohár [mailto:pali.ro...@gmail.com] Sent: Saturday, December 02, 2017 6:08 AM To: Masaki Ota <012ne...@gmail.com> Cc: dmitry.torok...@gmail.com;

RE: [PATCH] Support TrackStick of Thinkpad L570

Hi, Pali, I don't get your point. Please modify the code if you have an idea. Best Regards, Masaki Ota -Original Message- From: Pali Rohár [mailto:pali.ro...@gmail.com] Sent: Saturday, December 02, 2017 6:08 AM To: Masaki Ota <012ne...@gmail.com> Cc: dmitry.torok...@gmail.com;

[PATCH 1/1] mm/page_owner: ignore everything below the IRQ entry point

Check whether the allocation happens in an IRQ handler. This lets us strip everything below the IRQ entry point to reduce the number of unique stack traces needed to be stored. so moved code of KASAN in generic file so that page_owner can also do same filteration. Initial KASAN commit

[PATCH 1/1] mm/page_owner: ignore everything below the IRQ entry point

Check whether the allocation happens in an IRQ handler. This lets us strip everything below the IRQ entry point to reduce the number of unique stack traces needed to be stored. so moved code of KASAN in generic file so that page_owner can also do same filteration. Initial KASAN commit

Re: [PATCH v1] PCI: Make PCI_SCAN_ALL_PCIE_DEVS work for Root as well as Downstream Ports

Bjorn Helgaas writes: > On Fri, Dec 01, 2017 at 06:27:10PM -0600, Bjorn Helgaas wrote: >> From: Bjorn Helgaas >> >> PCIe Downstream Ports normally have only a Device 0 below them. To >> optimize enumeration, we don't scan for other devices *unless* the

Re: [PATCH v1] PCI: Make PCI_SCAN_ALL_PCIE_DEVS work for Root as well as Downstream Ports

Bjorn Helgaas writes: > On Fri, Dec 01, 2017 at 06:27:10PM -0600, Bjorn Helgaas wrote: >> From: Bjorn Helgaas >> >> PCIe Downstream Ports normally have only a Device 0 below them. To >> optimize enumeration, we don't scan for other devices *unless* the >> PCI_SCAN_ALL_PCIE_DEVS flag is set by

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Mon, 2017-12-04 at 11:11 +1100, Tobin C. Harding wrote: > On Fri, Dec 01, 2017 at 06:39:07PM +0530, kaiwan.billimo...@gmail.com wrote: > > @@ -267,7 +266,7 @@ sub is_false_positive > > sub is_false_positive_ix86_32 > > { > > my ($match) = @_; > > - state $page_offset =

Re: [PATCH] leaking_addresses: add support for 32-bit kernel addresses

On Mon, 2017-12-04 at 11:11 +1100, Tobin C. Harding wrote: > On Fri, Dec 01, 2017 at 06:39:07PM +0530, kaiwan.billimo...@gmail.com wrote: > > @@ -267,7 +266,7 @@ sub is_false_positive > > sub is_false_positive_ix86_32 > > { > > my ($match) = @_; > > - state $page_offset =

Re: [PATCH] powerpc/powernv : Add support to enable sensor groups

Shilpasri G Bhat writes: > On 11/28/2017 05:07 PM, Michael Ellerman wrote: >> Shilpasri G Bhat writes: >> >>> Adds support to enable/disable a sensor group. This can be used to >>> select the sensor groups that needs to be copied

Re: [PATCH] powerpc/powernv : Add support to enable sensor groups

Shilpasri G Bhat writes: > On 11/28/2017 05:07 PM, Michael Ellerman wrote: >> Shilpasri G Bhat writes: >> >>> Adds support to enable/disable a sensor group. This can be used to >>> select the sensor groups that needs to be copied to main memory by >>> OCC. Sensor groups like power, temperature,

Re: [PATCH v9 0/5] Add support for ThunderX2 pmu events using json files

Hi perf maintainers, can this be queued to -next?? please let me know, if have to rebase to any specific branch and send next version? On Mon, Nov 27, 2017 at 3:34 PM, John Garry wrote: > On 07/11/2017 01:23, Will Deacon wrote: >> >> Hi Arnaldo, >> >> On Tue, Oct 17,

Re: [PATCH v9 0/5] Add support for ThunderX2 pmu events using json files

Hi perf maintainers, can this be queued to -next?? please let me know, if have to rebase to any specific branch and send next version? On Mon, Nov 27, 2017 at 3:34 PM, John Garry wrote: > On 07/11/2017 01:23, Will Deacon wrote: >> >> Hi Arnaldo, >> >> On Tue, Oct 17, 2017 at 12:02:17AM +0530,

Re: KASAN: slab-out-of-bounds Read in strcmp

On Sun, 3 Dec 2017, Tetsuo Handa wrote: > Tetsuo Handa wrote: > > which will allow strcmp() to trigger out of bound read when "size" is > > larger than strlen(initial_sid_to_string[i]). > > Oops. "smaller" than. > > > > > Thus, I guess the simplest fix is to use strncmp() instead of strcmp().

Re: KASAN: slab-out-of-bounds Read in strcmp

On Sun, 3 Dec 2017, Tetsuo Handa wrote: > Tetsuo Handa wrote: > > which will allow strcmp() to trigger out of bound read when "size" is > > larger than strlen(initial_sid_to_string[i]). > > Oops. "smaller" than. > > > > > Thus, I guess the simplest fix is to use strncmp() instead of strcmp().

[rcu:rcu/dev 23/23] kernel//rcu/tree.c:2147:4: note: in expansion of macro 'pr_info'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/dev head: b4a12b9fc6e8c8e6b17b968b654f388a1379ce8a commit: b4a12b9fc6e8c8e6b17b968b654f388a1379ce8a [23/23] EXP: rcu: Add yet more debugging info to assertion config: arm-efm32_defconfig (attached as .config)

[rcu:rcu/dev 23/23] kernel//rcu/tree.c:2147:4: note: in expansion of macro 'pr_info'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/dev head: b4a12b9fc6e8c8e6b17b968b654f388a1379ce8a commit: b4a12b9fc6e8c8e6b17b968b654f388a1379ce8a [23/23] EXP: rcu: Add yet more debugging info to assertion config: arm-efm32_defconfig (attached as .config)

linux-next: Tree for Dec 4

Hi all, Changes since 20171201: New tree: nfs-anna Undropped tree: vfs The samsung-krzk tree gained a conflict against the keystone tree. The vfs tree lost its bad conflicts against Linus' tree but gained a (simple) conflict. It also gained a build failure for which I applied a patch.

linux-next: Tree for Dec 4

Hi all, Changes since 20171201: New tree: nfs-anna Undropped tree: vfs The samsung-krzk tree gained a conflict against the keystone tree. The vfs tree lost its bad conflicts against Linus' tree but gained a (simple) conflict. It also gained a build failure for which I applied a patch.

[PATCH v2 2/2] x86/apic: Update the 'apic=' description of setting APIC driver

There are two consumers of apic=: the APIC debug level and the low level generic architecture code, but Linux just documented the first one. Append the second description. Signed-off-by: Dou Liyang --- V1 --> V2: -Replcace the description suggested by Randy Dunlap

[PATCH v2 1/2] x86/apic: Avoid wrong warning when parsing 'apic=' in X86-32 case.

There are two consumers of apic=: apic_set_verbosity() for setting the APIC debug level; parse_apic() for registering APIC driver by hand. X86-32 supports both of them, but sometimes, kernel issues a weird warning. eg: when kernel was booted up with 'apic=bigsmp' in command line, early_param

[PATCH v2 2/2] x86/apic: Update the 'apic=' description of setting APIC driver

There are two consumers of apic=: the APIC debug level and the low level generic architecture code, but Linux just documented the first one. Append the second description. Signed-off-by: Dou Liyang --- V1 --> V2: -Replcace the description suggested by Randy Dunlap ---

[PATCH v2 1/2] x86/apic: Avoid wrong warning when parsing 'apic=' in X86-32 case.

There are two consumers of apic=: apic_set_verbosity() for setting the APIC debug level; parse_apic() for registering APIC driver by hand. X86-32 supports both of them, but sometimes, kernel issues a weird warning. eg: when kernel was booted up with 'apic=bigsmp' in command line, early_param

Re: [PATCH 1/5] bpf: correct broken uapi for BPF_PROG_TYPE_PERF_EVENT program type

Hi Hendrik, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2] [cannot apply to tip/perf/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/5] bpf: correct broken uapi for BPF_PROG_TYPE_PERF_EVENT program type

Hi Hendrik, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc2] [cannot apply to tip/perf/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [lkp-robot] [x86/entry/64] 63e02a2a32: will-it-scale.per_process_ops -13.0% regression

Thomas, has my fix for this landed? --Andy > On Dec 3, 2017, at 7:02 PM, kernel test robot wrote: > > > Greeting, > > FYI, we noticed a -13.0% regression of will-it-scale.per_process_ops due to > commit: > > > commit: 63e02a2a3292d8815eac7be438c8c73d72a7bb93

Re: [lkp-robot] [x86/entry/64] 63e02a2a32: will-it-scale.per_process_ops -13.0% regression

Thomas, has my fix for this landed? --Andy > On Dec 3, 2017, at 7:02 PM, kernel test robot wrote: > > > Greeting, > > FYI, we noticed a -13.0% regression of will-it-scale.per_process_ops due to > commit: > > > commit: 63e02a2a3292d8815eac7be438c8c73d72a7bb93 ("x86/entry/64: Create a >

Re: [alsa-devel] [PATCH v4 09/15] soundwire: Add slave status handling

On 12/3/17 9:21 PM, Vinod Koul wrote: On Sun, Dec 03, 2017 at 09:11:39PM -0600, Pierre-Louis Bossart wrote: On 12/3/17 11:11 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:52:03PM -0600, Pierre-Louis Bossart wrote: + status = sdw_read(slave, SDW_DP0_INT); + if

Re: [alsa-devel] [PATCH v4 09/15] soundwire: Add slave status handling

On 12/3/17 9:21 PM, Vinod Koul wrote: On Sun, Dec 03, 2017 at 09:11:39PM -0600, Pierre-Louis Bossart wrote: On 12/3/17 11:11 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:52:03PM -0600, Pierre-Louis Bossart wrote: + status = sdw_read(slave, SDW_DP0_INT); + if

Re: [PATCH] ext4: Support fast symlinks from ext3 file systems

On Mon, Nov 27, 2017 at 11:08:53AM -0700, Andreas Dilger wrote: > On Nov 27, 2017, at 10:37 AM, Andi Kleen wrote: > > > > From: Andi Kleen > > > > dbb3c27f5b91c4 (ext4: change fast symlink test to not rely on i_blocks) > > broke ~10 years old ext3

Re: [PATCH] ext4: Support fast symlinks from ext3 file systems

On Mon, Nov 27, 2017 at 11:08:53AM -0700, Andreas Dilger wrote: > On Nov 27, 2017, at 10:37 AM, Andi Kleen wrote: > > > > From: Andi Kleen > > > > dbb3c27f5b91c4 (ext4: change fast symlink test to not rely on i_blocks) > > broke ~10 years old ext3 file systems created by 2.6.17. Any ELF > >

Re: possible deadlock in blk_trace_remove

On Sun, 2017-12-03 at 17:47 -0700, Jens Axboe wrote: > On 12/03/2017 05:44 PM, Eric Biggers wrote: > > > >>> #syz fix: blktrace: fix trace mutex deadlock > >> > >> This is fixed in current -git. > >> > > > > I know, but syzbot needed to be told what commit fixes the bug. > > See

Re: possible deadlock in blk_trace_remove

On Sun, 2017-12-03 at 17:47 -0700, Jens Axboe wrote: > On 12/03/2017 05:44 PM, Eric Biggers wrote: > > > >>> #syz fix: blktrace: fix trace mutex deadlock > >> > >> This is fixed in current -git. > >> > > > > I know, but syzbot needed to be told what commit fixes the bug. > > See

Re: [PATCH v18 07/10] virtio-balloon: VIRTIO_BALLOON_F_SG

On 12/01/2017 11:38 PM, Michael S. Tsirkin wrote: On Wed, Nov 29, 2017 at 09:55:23PM +0800, Wei Wang wrote: +static void send_one_desc(struct virtio_balloon *vb, + struct virtqueue *vq, + uint64_t addr, + uint32_t len, +

Re: [PATCH v18 07/10] virtio-balloon: VIRTIO_BALLOON_F_SG

On 12/01/2017 11:38 PM, Michael S. Tsirkin wrote: On Wed, Nov 29, 2017 at 09:55:23PM +0800, Wei Wang wrote: +static void send_one_desc(struct virtio_balloon *vb, + struct virtqueue *vq, + uint64_t addr, + uint32_t len, +

Re: linux-next: Signed-off-by missing for commit in the arm-soc tree

Thanks, Stephen. I need to get a similar script going to catch these things in our own tree. Since this was a clean revert, I've redone it myself, carrying over descriptions from the pull request and keeping attribution to Kevin. Kevin; hope this is alright with you. We can revisit if not.

Re: linux-next: Signed-off-by missing for commit in the arm-soc tree

Thanks, Stephen. I need to get a similar script going to catch these things in our own tree. Since this was a clean revert, I've redone it myself, carrying over descriptions from the pull request and keeping attribution to Kevin. Kevin; hope this is alright with you. We can revisit if not.

Re: [PATCH] Revert "x86/apic: Remove init_bsp_APIC()"

Hi Ville, [...] So, the true thing I want to get is the log without the revert. or could you tell me the phenomenon and reason of your machine hang directly. :-) IIRC the last thing in the log is the "Hierarchical SRCU implementation." line, after which the CPU seems to start spinning

Re: [PATCH] Revert "x86/apic: Remove init_bsp_APIC()"

Hi Ville, [...] So, the true thing I want to get is the log without the revert. or could you tell me the phenomenon and reason of your machine hang directly. :-) IIRC the last thing in the log is the "Hierarchical SRCU implementation." line, after which the CPU seems to start spinning

[PATCH] fhandle: avoid -EINVAL if requested size is too large.

Lennart Poettering observes that if the newly increased MAX_HANDLE_SZ is exported to user space, and then used in an application running on an old kernel, name_to_handle_at() will report -EINVAL, which is unhelpful and inconsistent with the documentation. So: 1/ add a comment making it clear

[PATCH] fhandle: avoid -EINVAL if requested size is too large.

Lennart Poettering observes that if the newly increased MAX_HANDLE_SZ is exported to user space, and then used in an application running on an old kernel, name_to_handle_at() will report -EINVAL, which is unhelpful and inconsistent with the documentation. So: 1/ add a comment making it clear

[PATCH 3/3] bluetooth: hci_ll: Add optional nvmem MAC address source

This adds an optional nvmem consumer to get a MAC address from an external source. The MAC address is then set in the Bluetooth chip after the firmware has been loaded. This has been tested working with a TI CC2560A chip (in a LEGO MINDSTORMS EV3). Signed-off-by: David Lechner

[PATCH 3/3] bluetooth: hci_ll: Add optional nvmem MAC address source

This adds an optional nvmem consumer to get a MAC address from an external source. The MAC address is then set in the Bluetooth chip after the firmware has been loaded. This has been tested working with a TI CC2560A chip (in a LEGO MINDSTORMS EV3). Signed-off-by: David Lechner ---

[PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st

This adds optional nvmem consumer properties to the ti,wlink-st device tree bindings to allow specifying the Bluetooth MAC address. Signed-off-by: David Lechner --- Documentation/devicetree/bindings/net/ti,wilink-st.txt | 4 1 file changed, 4 insertions(+) diff --git

[PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st

This adds optional nvmem consumer properties to the ti,wlink-st device tree bindings to allow specifying the Bluetooth MAC address. Signed-off-by: David Lechner --- Documentation/devicetree/bindings/net/ti,wilink-st.txt | 4 1 file changed, 4 insertions(+) diff --git

[PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command

This adds a #define for the vendor-specific HCI command to set the baudrate instead of using the bare 0xff36 multiple times. Signed-off-by: David Lechner --- drivers/bluetooth/hci_ll.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git

[PATCH 0/3] bluetooth: hci_ll: Get MAC address from NVMEM

This series adds supporting getting the MAC address from a NVMEM provider for "LL" HCI controllers (Texas Instruments). The second patch is just cleaning things up before I add another similar vendor-specific HCI command constant in the final patch. David Lechner (3): dt-bindings: Add optional

[PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command

This adds a #define for the vendor-specific HCI command to set the baudrate instead of using the bare 0xff36 multiple times. Signed-off-by: David Lechner --- drivers/bluetooth/hci_ll.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/hci_ll.c

[PATCH 0/3] bluetooth: hci_ll: Get MAC address from NVMEM

This series adds supporting getting the MAC address from a NVMEM provider for "LL" HCI controllers (Texas Instruments). The second patch is just cleaning things up before I add another similar vendor-specific HCI command constant in the final patch. David Lechner (3): dt-bindings: Add optional

linux-next: build failure after merge of the mfd tree

Hi Lee, After merging the mfd tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3': (.text+0x5760): multiple definition of `.sd_power_off_card3v3' drivers/misc/cardreader/rtsx_pcr.o:(.text+0x4630): first defined

linux-next: build failure after merge of the mfd tree

Hi Lee, After merging the mfd tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3': (.text+0x5760): multiple definition of `.sd_power_off_card3v3' drivers/misc/cardreader/rtsx_pcr.o:(.text+0x4630): first defined

Re: [alsa-devel] [PATCH v4 09/15] soundwire: Add slave status handling

On Sun, Dec 03, 2017 at 09:11:39PM -0600, Pierre-Louis Bossart wrote: > On 12/3/17 11:11 AM, Vinod Koul wrote: > >On Fri, Dec 01, 2017 at 05:52:03PM -0600, Pierre-Louis Bossart wrote: > > > >>>+ status = sdw_read(slave, SDW_DP0_INT); > >>>+ if (status < 0) { > >>>+

Re: [alsa-devel] [PATCH v4 09/15] soundwire: Add slave status handling

On Sun, Dec 03, 2017 at 09:11:39PM -0600, Pierre-Louis Bossart wrote: > On 12/3/17 11:11 AM, Vinod Koul wrote: > >On Fri, Dec 01, 2017 at 05:52:03PM -0600, Pierre-Louis Bossart wrote: > > > >>>+ status = sdw_read(slave, SDW_DP0_INT); > >>>+ if (status < 0) { > >>>+

[PATCH 1/1] gianfar: fix a flooded alignment reports because of padding issue.

According to LS1021A RM, the value of PAL can be set so that the start of the IP header in the receive data buffer is aligned to a 32-bit boundary. Normally, setting PAL = 2 provides minimal padding to ensure such alignment of the IP header. However every incoming packet's 8-byte time stamp will

[PATCH 1/1] gianfar: fix a flooded alignment reports because of padding issue.

According to LS1021A RM, the value of PAL can be set so that the start of the IP header in the receive data buffer is aligned to a 32-bit boundary. Normally, setting PAL = 2 provides minimal padding to ensure such alignment of the IP header. However every incoming packet's 8-byte time stamp will

Re: [alsa-devel] [PATCH v4 09/15] soundwire: Add slave status handling

On 12/3/17 11:11 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:52:03PM -0600, Pierre-Louis Bossart wrote: + status = sdw_read(slave, SDW_DP0_INT); + if (status < 0) { + dev_err(slave->bus->dev, + "SDW_DP0_INT

Re: [alsa-devel] [PATCH v4 09/15] soundwire: Add slave status handling

On 12/3/17 11:11 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:52:03PM -0600, Pierre-Louis Bossart wrote: + status = sdw_read(slave, SDW_DP0_INT); + if (status < 0) { + dev_err(slave->bus->dev, + "SDW_DP0_INT

Re: [PATCH] riscv/ftrace: Add basic support

On Thu, Nov 30, 2017 at 12:31:53PM +0100, Philippe Ombredanne wrote: > On Thu, Nov 30, 2017 at 9:53 AM, Alan Kao wrote: > [] > > diff --git a/arch/riscv/include/asm/ftrace.h > > b/arch/riscv/include/asm/ftrace.h > > new file mode 100644 > > index ..38beadb07ad5 >

Re: [PATCH] riscv/ftrace: Add basic support

On Thu, Nov 30, 2017 at 12:31:53PM +0100, Philippe Ombredanne wrote: > On Thu, Nov 30, 2017 at 9:53 AM, Alan Kao wrote: > [] > > diff --git a/arch/riscv/include/asm/ftrace.h > > b/arch/riscv/include/asm/ftrace.h > > new file mode 100644 > > index ..38beadb07ad5 > > --- /dev/null > >

Re: [alsa-devel] [PATCH v4 08/15] soundwire: Add Slave status handling helpers

On Sun, Dec 03, 2017 at 09:07:29PM -0600, Pierre-Louis Bossart wrote: > On 12/3/17 11:08 AM, Vinod Koul wrote: > >On Fri, Dec 01, 2017 at 05:36:47PM -0600, Pierre-Louis Bossart wrote: > > > >>>+/* called with bus_lock held */ > >>>+static int sdw_get_device_num(struct sdw_slave *slave) > >>>+{ >

Re: [alsa-devel] [PATCH v4 08/15] soundwire: Add Slave status handling helpers

On Sun, Dec 03, 2017 at 09:07:29PM -0600, Pierre-Louis Bossart wrote: > On 12/3/17 11:08 AM, Vinod Koul wrote: > >On Fri, Dec 01, 2017 at 05:36:47PM -0600, Pierre-Louis Bossart wrote: > > > >>>+/* called with bus_lock held */ > >>>+static int sdw_get_device_num(struct sdw_slave *slave) > >>>+{ >

Re: [alsa-devel] [PATCH v4 08/15] soundwire: Add Slave status handling helpers

On 12/3/17 11:08 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:36:47PM -0600, Pierre-Louis Bossart wrote: +/* called with bus_lock held */ +static int sdw_get_device_num(struct sdw_slave *slave) +{ + int bit; + + bit = find_first_zero_bit(slave->bus->assigned, SDW_MAX_DEVICES);

Re: [alsa-devel] [PATCH v4 08/15] soundwire: Add Slave status handling helpers

On 12/3/17 11:08 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:36:47PM -0600, Pierre-Louis Bossart wrote: +/* called with bus_lock held */ +static int sdw_get_device_num(struct sdw_slave *slave) +{ + int bit; + + bit = find_first_zero_bit(slave->bus->assigned, SDW_MAX_DEVICES);

Re: [alsa-devel] [PATCH v4 06/15] soundwire: Add IO transfer

On 12/3/17 11:04 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:27:31PM -0600, Pierre-Louis Bossart wrote: +static inline int find_response_code(enum sdw_command_response resp) +{ + switch (resp) { + case SDW_CMD_OK: + return 0; + + case SDW_CMD_IGNORED: +

Re: [alsa-devel] [PATCH v4 06/15] soundwire: Add IO transfer

On 12/3/17 11:04 AM, Vinod Koul wrote: On Fri, Dec 01, 2017 at 05:27:31PM -0600, Pierre-Louis Bossart wrote: +static inline int find_response_code(enum sdw_command_response resp) +{ + switch (resp) { + case SDW_CMD_OK: + return 0; + + case SDW_CMD_IGNORED: +

[PATCH v7 04/11] asm-generic: add kexec_file_load system call to unistd.h

The initial user of this system call number is arm64. Signed-off-by: AKASHI Takahiro Acked-by: Arnd Bergmann --- include/uapi/asm-generic/unistd.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/uapi/asm-generic/unistd.h

[PATCH v7 04/11] asm-generic: add kexec_file_load system call to unistd.h

The initial user of this system call number is arm64. Signed-off-by: AKASHI Takahiro Acked-by: Arnd Bergmann --- include/uapi/asm-generic/unistd.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h index

[PATCH v7 08/11] arm64: kexec_file: enable KEXEC_FILE config

Modify arm64/Kconfig and Makefile to enable kexec_file_load support. File-format specific hook functions to load a kernel image will follow this patch. Signed-off-by: AKASHI Takahiro Cc: Catalin Marinas Cc: Will Deacon

[PATCH v7 08/11] arm64: kexec_file: enable KEXEC_FILE config

Modify arm64/Kconfig and Makefile to enable kexec_file_load support. File-format specific hook functions to load a kernel image will follow this patch. Signed-off-by: AKASHI Takahiro Cc: Catalin Marinas Cc: Will Deacon --- arch/arm64/Kconfig | 13 + 1 file changed, 13

[PATCH v7 09/11] arm64: kexec_file: add Image format support

The "Image" binary will be loaded at the offset of TEXT_OFFSET from the start of system memory. TEXT_OFFSET is determined from the header of the image. This patch doesn't have CONFIG_KEXEC_VERIFY_SIG support. Nevertherless kernel verification will be supported by enabling IMA security subsystem.

[PATCH v7 09/11] arm64: kexec_file: add Image format support

The "Image" binary will be loaded at the offset of TEXT_OFFSET from the start of system memory. TEXT_OFFSET is determined from the header of the image. This patch doesn't have CONFIG_KEXEC_VERIFY_SIG support. Nevertherless kernel verification will be supported by enabling IMA security subsystem.

[PATCH v7 11/11] arm64: kexec_file: enable KEXEC_VERIFY_SIG for Image

With this patch, kernel verification can be done without IMA security subsystem enabled. Turn on CONFIG_KEXEC_VERIFY_SIG instead. On x86, a signature is embedded into a PE file (Microsoft's format) header of binary. Since arm64's "Image" can also be seen as a PE file as far as CONFIG_EFI is

[PATCH v7 10/11] include: pe.h: remove message[] from mz header definition

message[] field won't be part of the definition of mz header. This change is crucial for enabling kexec_file_load on arm64 because arm64's "Image" binary, as in PE format, doesn't have any data for it and accordingly the following check in pefile_parse_binary() will fail: chkaddr(cursor,

[PATCH v7 11/11] arm64: kexec_file: enable KEXEC_VERIFY_SIG for Image

With this patch, kernel verification can be done without IMA security subsystem enabled. Turn on CONFIG_KEXEC_VERIFY_SIG instead. On x86, a signature is embedded into a PE file (Microsoft's format) header of binary. Since arm64's "Image" can also be seen as a PE file as far as CONFIG_EFI is

[PATCH v7 10/11] include: pe.h: remove message[] from mz header definition

message[] field won't be part of the definition of mz header. This change is crucial for enabling kexec_file_load on arm64 because arm64's "Image" binary, as in PE format, doesn't have any data for it and accordingly the following check in pefile_parse_binary() will fail: chkaddr(cursor,

<    1   2   3   4   5   6   7   >