Six fixes for mostly minor issues, most of which have small race
windows for occurring.
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
The short changelog is:
Bart Van Assche (1):
scsi: Suppress a kernel warning in case the prep
Six fixes for mostly minor issues, most of which have small race
windows for occurring.
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
The short changelog is:
Bart Van Assche (1):
scsi: Suppress a kernel warning in case the prep
Hi Hannes,
Thank you for looking into the issue. If there is anything I can help
to test the patch? I appreciate your help. Thank you.
On Fri, Oct 6, 2017 at 9:08 AM, Gavin Guo wrote:
> On Mon, Oct 2, 2017 at 10:32 PM, Hannes Reinecke wrote:
>> On
Hi Hannes,
Thank you for looking into the issue. If there is anything I can help
to test the patch? I appreciate your help. Thank you.
On Fri, Oct 6, 2017 at 9:08 AM, Gavin Guo wrote:
> On Mon, Oct 2, 2017 at 10:32 PM, Hannes Reinecke wrote:
>> On 09/27/2017 09:33 AM, Gavin Guo wrote:
>>>
Jia-Ju Bai wrote:
> No rcu_read_lock is called, but rcu_read_unlock is still called.
> Thus rcu_read_unlock should be removed.
>
> Signed-off-by: Jia-Ju Bai
> Acked-by: Bjorn Andersson
> Signed-off-by: Kalle Valo
Jia-Ju Bai wrote:
> No rcu_read_lock is called, but rcu_read_unlock is still called.
> Thus rcu_read_unlock should be removed.
>
> Signed-off-by: Jia-Ju Bai
> Acked-by: Bjorn Andersson
> Signed-off-by: Kalle Valo
Patch applied to ath-current branch of ath.git, thanks.
c0d5adc35c0b wcn36xx:
On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic Weisbecker wrote:
> + isolcpus= [KNL,SMP] Isolate a given set of CPUs from disturbance.
> + Format: [flag-list,]
> +
> + Specify one or more CPUs to isolate from disturbances
> +
On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic Weisbecker wrote:
> + isolcpus= [KNL,SMP] Isolate a given set of CPUs from disturbance.
> + Format: [flag-list,]
> +
> + Specify one or more CPUs to isolate from disturbances
> +
On Fri, Oct 27, 2017 at 06:49:55AM +, Reshetova, Elena wrote:
> Could we possibly have a bit more elaborate discussion on this?
>
> Or alternatively, what then should be the correct way for a certain
> variable (that behaves like a standard refcounter) to check if the
> relaxed memory
On Fri, Oct 27, 2017 at 06:49:55AM +, Reshetova, Elena wrote:
> Could we possibly have a bit more elaborate discussion on this?
>
> Or alternatively, what then should be the correct way for a certain
> variable (that behaves like a standard refcounter) to check if the
> relaxed memory
This adds support for IP version 5 of DWMAC. The new introduced
features are the Enhancements to Scheduled Traffic (EST) as
defined by IEEE802.1Qbv-2015 and Frame Preemption (FPE) as
defined by IEEE802.1Qbu.
In order to not break previous setups all the necessary
configuration is only performed
This adds support for IP version 5 of DWMAC. The new introduced
features are the Enhancements to Scheduled Traffic (EST) as
defined by IEEE802.1Qbv-2015 and Frame Preemption (FPE) as
defined by IEEE802.1Qbu.
In order to not break previous setups all the necessary
configuration is only performed
Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly.
>
> Cc: Kalle Valo
> Cc:
Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly.
>
> Cc: Kalle Valo
> Cc: linux-wirel...@vger.kernel.org
> Cc:
On Thu, 26 Oct 2017, Andy Lutomirski wrote:
> diff --git a/arch/x86/include/asm/processor.h
> b/arch/x86/include/asm/processor.h
> index b390ff76e58f..0167e3e35a57 100644
> --- a/arch/x86/include/asm/processor.h
> +++ b/arch/x86/include/asm/processor.h
> @@ -520,13 +520,6 @@ static inline void
>
On Thu, 26 Oct 2017, Andy Lutomirski wrote:
> diff --git a/arch/x86/include/asm/processor.h
> b/arch/x86/include/asm/processor.h
> index b390ff76e58f..0167e3e35a57 100644
> --- a/arch/x86/include/asm/processor.h
> +++ b/arch/x86/include/asm/processor.h
> @@ -520,13 +520,6 @@ static inline void
>
Christos Gkekas wrote:
> Variable val is unsigned, so checking whether it is less than zero is
> redundant.
>
> Signed-off-by: Christos Gkekas
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git,
Christos Gkekas wrote:
> Variable val is unsigned, so checking whether it is less than zero is
> redundant.
>
> Signed-off-by: Christos Gkekas
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
9d414949a306 ath9k: debug: Remove redundant check
--
Hi Peppe,
On 27-10-2017 13:29, Giuseppe CAVALLARO wrote:
> Hello
>
> On 10/27/2017 11:05 AM, Jose Abreu wrote:
>> I think we should take advantage of the fact that this is working
>> and ready to be merged. Its just HW configuration but maybe it
>> can serve as momentum for other drivers to also
Hi Peppe,
On 27-10-2017 13:29, Giuseppe CAVALLARO wrote:
> Hello
>
> On 10/27/2017 11:05 AM, Jose Abreu wrote:
>> I think we should take advantage of the fact that this is working
>> and ready to be merged. Its just HW configuration but maybe it
>> can serve as momentum for other drivers to also
Christos Gkekas wrote:
> Variable val is unsigned, so checking whether it is less than zero is
> redundant.
>
> Signed-off-by: Christos Gkekas
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git,
Christos Gkekas wrote:
> Variable val is unsigned, so checking whether it is less than zero is
> redundant.
>
> Signed-off-by: Christos Gkekas
> Signed-off-by: Kalle Valo
Patch applied to ath-next branch of ath.git, thanks.
d83c0d3293bb ath10k: spectral: remove redundant check in
Hi Egil,
Egil Hjelmeland writes:
> > The DSA code currently has 3 bitmaps in the dsa_switch structure:
> > cpu_port_mask, dsa_port_mask and enabled_port_mask.
>
>
> First I must apologize to everybody for not replying in-thread. Problem
> is that I was not
Brian Norris wrote:
> Build errors have been reported with CONFIG_PM=n:
>
> drivers/net/wireless/ath/ath10k/pci.c:3416:8: error: implicit
> declaration of function 'ath10k_pci_suspend'
> [-Werror=implicit-function-declaration]
>
>
Hi Egil,
Egil Hjelmeland writes:
> > The DSA code currently has 3 bitmaps in the dsa_switch structure:
> > cpu_port_mask, dsa_port_mask and enabled_port_mask.
>
>
> First I must apologize to everybody for not replying in-thread. Problem
> is that I was not subscribed to netdev. But now I am,
Brian Norris wrote:
> Build errors have been reported with CONFIG_PM=n:
>
> drivers/net/wireless/ath/ath10k/pci.c:3416:8: error: implicit
> declaration of function 'ath10k_pci_suspend'
> [-Werror=implicit-function-declaration]
>
> drivers/net/wireless/ath/ath10k/pci.c:3428:8: error: implicit
>
>> @@ -329,6 +325,10 @@ static int palmas_gpadc_calibrate(struct palmas_gpadc
>> *adc, int adc_chan)
>>
>> scrub:
>> return ret;
>> +
>> +report_failure:
>
> This makes for complex code flow where it is not needed.
The shown code layout would be required in the suggested software design
>> @@ -329,6 +325,10 @@ static int palmas_gpadc_calibrate(struct palmas_gpadc
>> *adc, int adc_chan)
>>
>> scrub:
>> return ret;
>> +
>> +report_failure:
>
> This makes for complex code flow where it is not needed.
The shown code layout would be required in the suggested software design
>>>
>>> -#define CMD_ERRORS \
>>> - (R1_OUT_OF_RANGE | /* Command argument out of range */ \
>>> -R1_ADDRESS_ERROR | /* Misaligned address */\
>>> +#define CMD_ERRORS_EXCL_OOR
>>>
>>> -#define CMD_ERRORS \
>>> - (R1_OUT_OF_RANGE | /* Command argument out of range */ \
>>> -R1_ADDRESS_ERROR | /* Misaligned address */\
>>> +#define CMD_ERRORS_EXCL_OOR
On Fri 27-10-17 11:44:58, Dmitry Vyukov wrote:
> On Fri, Oct 27, 2017 at 11:34 AM, Michal Hocko wrote:
> > On Fri 27-10-17 02:22:40, syzbot wrote:
> >> Hello,
> >>
> >> syzkaller hit the following crash on
> >> a31cc455c512f3f1dd5f79cac8e29a7c8a617af8
> >>
On 10/27/2017 12:54 AM, Eric Long wrote:
Hi Guenter,
Thanks for you commonts.
On Thu, Oct 26, 2017 at 10:23:40PM -0700, Guenter Roeck wrote:
On 10/26/2017 07:28 PM, Eric Long wrote:
This patch adds the watchdog driver for Spreadtrum SC9860 platform.
Signed-off-by: Eric Long
On Fri 27-10-17 11:44:58, Dmitry Vyukov wrote:
> On Fri, Oct 27, 2017 at 11:34 AM, Michal Hocko wrote:
> > On Fri 27-10-17 02:22:40, syzbot wrote:
> >> Hello,
> >>
> >> syzkaller hit the following crash on
> >> a31cc455c512f3f1dd5f79cac8e29a7c8a617af8
> >>
On 10/27/2017 12:54 AM, Eric Long wrote:
Hi Guenter,
Thanks for you commonts.
On Thu, Oct 26, 2017 at 10:23:40PM -0700, Guenter Roeck wrote:
On 10/26/2017 07:28 PM, Eric Long wrote:
This patch adds the watchdog driver for Spreadtrum SC9860 platform.
Signed-off-by: Eric Long
---
Change
On (10/26/17 13:53), Tobin C. Harding wrote:
> Currently there are many places in the kernel where addresses are being
> printed using an unadorned %p. Kernel pointers should be printed using
> %pK allowing some control via the kptr_restrict sysctl. Exposing
> addresses gives attackers sensitive
On (10/26/17 13:53), Tobin C. Harding wrote:
> Currently there are many places in the kernel where addresses are being
> printed using an unadorned %p. Kernel pointers should be printed using
> %pK allowing some control via the kptr_restrict sysctl. Exposing
> addresses gives attackers sensitive
On 2017/10/27 20:33, Borislav Petkov wrote:
On Fri, Oct 27, 2017 at 07:42:45PM +0800, zhouchengming wrote:
This is a real bug happened on one of our machines, below is the calltrace.
We can see the trigger is at alternatives_text_reserved+0x20/0x80, and
encounter a deleted (poisoned) list_head.
On 2017/10/27 20:33, Borislav Petkov wrote:
On Fri, Oct 27, 2017 at 07:42:45PM +0800, zhouchengming wrote:
This is a real bug happened on one of our machines, below is the calltrace.
We can see the trigger is at alternatives_text_reserved+0x20/0x80, and
encounter a deleted (poisoned) list_head.
On asus T100, Capella cm3218 chip is implemented as ambiant light
sensor. This chip expose an smbus ARA protocol device on standard
address 0x0c. The chip is not functional before all alerts are
acknowledged.
On asus T100, this device is enumerated on ACPI bus and the description
give tow I2C
On asus T100, Capella cm3218 chip is implemented as ambiant light
sensor. This chip expose an smbus ARA protocol device on standard
address 0x0c. The chip is not functional before all alerts are
acknowledged.
On asus T100, this device is enumerated on ACPI bus and the description
give tow I2C
On Thu, Oct 26, 2017 at 10:36:47AM +0200, Cornelia Huck wrote:
> On Thu, 26 Oct 2017 04:48:01 +0300
> "Michael S. Tsirkin" wrote:
>
> > last kicked event index must be updated unconditionally:
> > even if we don't need to kick, we do not want to re-check
> > the same entry for
On Thu, Oct 26, 2017 at 10:36:47AM +0200, Cornelia Huck wrote:
> On Thu, 26 Oct 2017 04:48:01 +0300
> "Michael S. Tsirkin" wrote:
>
> > last kicked event index must be updated unconditionally:
> > even if we don't need to kick, we do not want to re-check
> > the same entry for events.
> >
> >
> Same issue - readability is worse
An alternative opinion triggered the development also of this update suggestion.
> than without the patch so it is always going to be rejected.
Corresponding clarification might be needed if the change (in a direction
I propose here) will become desirable.
> Same issue - readability is worse
An alternative opinion triggered the development also of this update suggestion.
> than without the patch so it is always going to be rejected.
Corresponding clarification might be needed if the change (in a direction
I propose here) will become desirable.
last kicked event index must be updated unconditionally:
even if we don't need to kick, we do not want to re-check
the same entry for events.
Reported-by: Cornelia Huck
Signed-off-by: Michael S. Tsirkin
---
tools/virtio/ringtest/virtio_ring_0_9.c | 24
last kicked event index must be updated unconditionally:
even if we don't need to kick, we do not want to re-check
the same entry for events.
Reported-by: Cornelia Huck
Signed-off-by: Michael S. Tsirkin
---
tools/virtio/ringtest/virtio_ring_0_9.c | 24 ++--
1 file changed,
> If someone knows how to fix the backlight, it would still be useful.
In panel-dsi-cm.c it's set to maximum with
dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 0xff);
Sebastian suggested the same but used 100 instead of 0xff, which might
be a bit too low. You can also add msleep(1000) after
> If someone knows how to fix the backlight, it would still be useful.
In panel-dsi-cm.c it's set to maximum with
dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 0xff);
Sebastian suggested the same but used 100 instead of 0xff, which might
be a bit too low. You can also add msleep(1000) after
On Fri, 2017-10-27 at 02:19 -0700, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly. Includes a fix for correcting an
> on-stack timer
On Fri, 2017-10-27 at 02:19 -0700, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly. Includes a fix for correcting an
> on-stack timer
Hi Andrew,
On jeu., oct. 19 2017, Andrew Lunn wrote:
> On Thu, Oct 19, 2017 at 03:10:03PM +0200, Gregory CLEMENT wrote:
>> From: Ken Ma
>>
>> Current edge both type gpio irqs which need to swap polarity in each
>> interrupt are not supported, this patch
Hi Andrew,
On jeu., oct. 19 2017, Andrew Lunn wrote:
> On Thu, Oct 19, 2017 at 03:10:03PM +0200, Gregory CLEMENT wrote:
>> From: Ken Ma
>>
>> Current edge both type gpio irqs which need to swap polarity in each
>> interrupt are not supported, this patch adds edge both type gpio irq
>>
> The DSA code currently has 3 bitmaps in the dsa_switch structure:
> cpu_port_mask, dsa_port_mask and enabled_port_mask.
Hi Vivien
First I must apologize to everybody for not replying in-thread. Problem
is that I was not subscribed to netdev. But now I am, so I promise it
will not happen
> The DSA code currently has 3 bitmaps in the dsa_switch structure:
> cpu_port_mask, dsa_port_mask and enabled_port_mask.
Hi Vivien
First I must apologize to everybody for not replying in-thread. Problem
is that I was not subscribed to netdev. But now I am, so I promise it
will not happen
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus
Fix several issues, most of them introduced in the last release.
Thanks,
Miklos
---
Amir Goldstein (3):
ovl: fix EIO from lookup of non-indexed upper
ovl: handle ENOENT on
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus
Fix several issues, most of them introduced in the last release.
Thanks,
Miklos
---
Amir Goldstein (3):
ovl: fix EIO from lookup of non-indexed upper
ovl: handle ENOENT on
It supports to extend reserved_blocks sysfs interface to be soft
threshold, which allows user configure it exceeding current available
user space. This patch also introduces a new sysfs interface called
current_reserved_blocks, which shows the current blocks that have
already been reserved.
It supports to extend reserved_blocks sysfs interface to be soft
threshold, which allows user configure it exceeding current available
user space. This patch also introduces a new sysfs interface called
current_reserved_blocks, which shows the current blocks that have
already been reserved.
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This fixes a longstanding bug, which can be triggered by interrupting a
directory reading syscall.
Thanks,
Miklos
---
Miklos Szeredi (1):
fuse: fix READDIRPLUS skipping an entry
---
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This fixes a longstanding bug, which can be triggered by interrupting a
directory reading syscall.
Thanks,
Miklos
---
Miklos Szeredi (1):
fuse: fix READDIRPLUS skipping an entry
---
This patch provides a new function to find a carveout according
to a device address (da).
If match found, this function returns CPU virtual address corresponding
to specified da.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_core.c | 42
This patch provides a new function to find a carveout according
to a device address (da).
If match found, this function returns CPU virtual address corresponding
to specified da.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_core.c | 42
1
Current version of rproc_alloc_vring function supports only dynamic vring
allocation.
This patch extends rproc_alloc_vring to verify if requested vring DA is
already part or not of a registered carveout. If true, nothing to do, else
just allocate vring as before.
Signed-off-by: Loic Pallardy
Current version of rproc_alloc_vring function supports only dynamic vring
allocation.
This patch extends rproc_alloc_vring to verify if requested vring DA is
already part or not of a registered carveout. If true, nothing to do, else
just allocate vring as before.
Signed-off-by: Loic Pallardy
---
The aim of the series is to implement carveout memory management as
discussed during OpenAMP weekly call and defined in proposed document [1]
This first series focus only on adding support of the different types of
carveout memories (dynamic, fixed, platform driver depend...).
64bit resource
In current version rproc_handle_carveout function support only dynamic
region allocation.
This patch extends rproc_handle_carveout function to support different carveout
configurations:
- fixed DA and fixed PA: check if already part of pre-registered carveouts
(platform driver). If no, return
This patch introduces a new API to allow platform driver to register
platform specific carveout regions.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_core.c | 22 ++
drivers/remoteproc/remoteproc_internal.h | 7 +++
In current version rproc_handle_carveout function support only dynamic
region allocation.
This patch extends rproc_handle_carveout function to support different carveout
configurations:
- fixed DA and fixed PA: check if already part of pre-registered carveouts
(platform driver). If no, return
This patch introduces a new API to allow platform driver to register
platform specific carveout regions.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_core.c | 22 ++
drivers/remoteproc/remoteproc_internal.h | 7 +++
include/linux/remoteproc.h
The aim of the series is to implement carveout memory management as
discussed during OpenAMP weekly call and defined in proposed document [1]
This first series focus only on adding support of the different types of
carveout memories (dynamic, fixed, platform driver depend...).
64bit resource
ST remote processor needs some specified memory regions for firmware and IPC.
Memory regions are defined as reserved memory and should be registered in
remoteproc core thanks to rproc_add_carveout function.
Memory region release is handled by ST driver itself on remove operation.
Signed-off-by:
ST remote processor needs some specified memory regions for firmware and IPC.
Memory regions are defined as reserved memory and should be registered in
remoteproc core thanks to rproc_add_carveout function.
Memory region release is handled by ST driver itself on remove operation.
Signed-off-by:
This new function translates CPU virtual address in
CPU physical one according to virtual address location.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_core.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git
Memory entry could be allocated in different ways (ioremap,
dma_alloc_coherent, internal RAM allocator...).
This patch introduces a release ops in rproc_mem_entry structure
to associate dedicated release mechanism to each memory entry descriptor
in order to keep remoteproc core generic.
This new function translates CPU virtual address in
CPU physical one according to virtual address location.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_core.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git
Memory entry could be allocated in different ways (ioremap,
dma_alloc_coherent, internal RAM allocator...).
This patch introduces a release ops in rproc_mem_entry structure
to associate dedicated release mechanism to each memory entry descriptor
in order to keep remoteproc core generic.
This patch adds the capability to display the content of
the resource table associated to a remote processor firmware.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_debugfs.c | 99 +
1 file changed, 99 insertions(+)
diff
This patch offers the capability to dump memory carveouts associated
to one remoteprocessor.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_debugfs.c | 31 +++
1 file changed, 31 insertions(+)
diff --git
This patch adds the capability to display the content of
the resource table associated to a remote processor firmware.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_debugfs.c | 99 +
1 file changed, 99 insertions(+)
diff --git
This patch offers the capability to dump memory carveouts associated
to one remoteprocessor.
Signed-off-by: Loic Pallardy
---
drivers/remoteproc/remoteproc_debugfs.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/remoteproc/remoteproc_debugfs.c
Hi Wenyou,
Unfortunately the v4 patch series was just merged instead of v5. Can you make a
new
patch applying just the v4 -> v5 changes?
Thanks!
Hans
On 10/27/2017 05:21 AM, Wenyou Yang wrote:
> To improve the readability of code, rework the format list table,
> split the format array
Hi Wenyou,
Unfortunately the v4 patch series was just merged instead of v5. Can you make a
new
patch applying just the v4 -> v5 changes?
Thanks!
Hans
On 10/27/2017 05:21 AM, Wenyou Yang wrote:
> To improve the readability of code, rework the format list table,
> split the format array
This series increases remoteproc debug capabilities by adding:
- associated resource table dump feature
- registered carveouts list dump feature
Loic Pallardy (2):
remoteproc: debug: add resource table dump feature
remoteproc: debug: add carveouts list dump feature
This series increases remoteproc debug capabilities by adding:
- associated resource table dump feature
- registered carveouts list dump feature
Loic Pallardy (2):
remoteproc: debug: add resource table dump feature
remoteproc: debug: add carveouts list dump feature
On 2017/10/27 19:47, Yunlong Song wrote:
> It supports to extend reserved_blocks sysfs interface to be soft
> threshold, which allows user configure it exceeding current available
> user space. This patch also introduces a new sysfs interface called
> current_reserved_blocks, which shows the
>> But I proposed an other source code layout for useful reasons.
>
> I think there is a (hidden) cost of having pure cleanup patches:
> they make backporting fixes harder (across the cleanup)
There the usual software development consequences to consider
if you dare to change the source code at
On 2017/10/27 19:47, Yunlong Song wrote:
> It supports to extend reserved_blocks sysfs interface to be soft
> threshold, which allows user configure it exceeding current available
> user space. This patch also introduces a new sysfs interface called
> current_reserved_blocks, which shows the
>> But I proposed an other source code layout for useful reasons.
>
> I think there is a (hidden) cost of having pure cleanup patches:
> they make backporting fixes harder (across the cleanup)
There the usual software development consequences to consider
if you dare to change the source code at
On Fri, Oct 27, 2017 at 07:42:45PM +0800, zhouchengming wrote:
> This is a real bug happened on one of our machines, below is the calltrace.
> We can see the trigger is at alternatives_text_reserved+0x20/0x80, and
> encounter a deleted (poisoned) list_head.
Looks like some out-of-tree, old kernel
On Fri, Oct 27, 2017 at 07:42:45PM +0800, zhouchengming wrote:
> This is a real bug happened on one of our machines, below is the calltrace.
> We can see the trigger is at alternatives_text_reserved+0x20/0x80, and
> encounter a deleted (poisoned) list_head.
Looks like some out-of-tree, old kernel
If there is no SFP module plugged into a port of mlx5 cards
'cat /sys/class/infniband/mlx5_X/ports/1/rate' returns Invalid argument.
This causes tools like 'ibstat' to malfunction. This change adjusts mlx5
to all other RoCE/iWarp drivers, which always return valid speed/width.
Signed-off-by:
If there is no SFP module plugged into a port of mlx5 cards
'cat /sys/class/infniband/mlx5_X/ports/1/rate' returns Invalid argument.
This causes tools like 'ibstat' to malfunction. This change adjusts mlx5
to all other RoCE/iWarp drivers, which always return valid speed/width.
Signed-off-by:
Hello
On 10/27/2017 11:05 AM, Jose Abreu wrote:
I think we should take advantage of the fact that this is working
and ready to be merged. Its just HW configuration but maybe it
can serve as momentum for other drivers to also integrate this?
Let me propose to have it now in the next-next.
Hello
On 10/27/2017 11:05 AM, Jose Abreu wrote:
I think we should take advantage of the fact that this is working
and ready to be merged. Its just HW configuration but maybe it
can serve as momentum for other drivers to also integrate this?
Let me propose to have it now in the next-next.
On Fri, Oct 27, 2017 at 02:23:07PM +0530, Neeraj Upadhyay wrote:
> Hi,
>
> One query regarding srcu_funnel_exp_start() function in
> kernel/rcu/srcutree.c.
>
> static void srcu_funnel_exp_start(struct srcu_struct *sp, struct
> srcu_node *snp,
> unsigned long s)
>
On Fri, Oct 27, 2017 at 02:23:07PM +0530, Neeraj Upadhyay wrote:
> Hi,
>
> One query regarding srcu_funnel_exp_start() function in
> kernel/rcu/srcutree.c.
>
> static void srcu_funnel_exp_start(struct srcu_struct *sp, struct
> srcu_node *snp,
> unsigned long s)
>
On Fri, Oct 27, 2017 at 02:15:03PM +0800, Kaihua Zhong wrote:
> Hi3660 mailbox controller is used to send message within multiple
> processors, MCU, HIFI, etc. It supports 32 mailbox channels and every
> channel can only be used for single transferring direction. Once the
> channel is enabled,
On Fri, Oct 27, 2017 at 02:15:03PM +0800, Kaihua Zhong wrote:
> Hi3660 mailbox controller is used to send message within multiple
> processors, MCU, HIFI, etc. It supports 32 mailbox channels and every
> channel can only be used for single transferring direction. Once the
> channel is enabled,
Commit-ID: 7d9285e82db5defca4d9674ba089429eeca0c697
Gitweb: https://git.kernel.org/tip/7d9285e82db5defca4d9674ba089429eeca0c697
Author: Yonghong Song
AuthorDate: Thu, 5 Oct 2017 09:19:19 -0700
Committer: Ingo Molnar
CommitDate: Fri, 27 Oct 2017 10:31:56
Commit-ID: 7d9285e82db5defca4d9674ba089429eeca0c697
Gitweb: https://git.kernel.org/tip/7d9285e82db5defca4d9674ba089429eeca0c697
Author: Yonghong Song
AuthorDate: Thu, 5 Oct 2017 09:19:19 -0700
Committer: Ingo Molnar
CommitDate: Fri, 27 Oct 2017 10:31:56 +0200
perf/bpf: Extend the
801 - 900 of 1392 matches
Mail list logo