Hi -
Need help to understand if below is something we should consider to be
fixed in megaraid_sas driver or call as unreal exposure.
I have created slice VD of size 10GB (raid 1) using 2 drives. Each
Physical Drive size is 256GB.
Last LBA of the VD and actual Physical disk associated with
On Wed, Mar 08, 2017 at 02:00:56PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 20:20:45 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the
Hi -
Need help to understand if below is something we should consider to be
fixed in megaraid_sas driver or call as unreal exposure.
I have created slice VD of size 10GB (raid 1) using 2 drives. Each
Physical Drive size is 256GB.
Last LBA of the VD and actual Physical disk associated with
On Wed, Mar 08, 2017 at 02:00:56PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 20:20:45 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination
On Tue, Feb 21, 2017 at 9:53 PM, Sven Rebhan wrote:
> Like other Lenovo models the Lenovo ideapad 310-15IKB does not have a
> hw rfkill switch. This results in hard-blocked radios after boot,
> resulting in always blocked radios rendering them unusable.
>
> The attached
On Tue, Feb 21, 2017 at 9:53 PM, Sven Rebhan wrote:
> Like other Lenovo models the Lenovo ideapad 310-15IKB does not have a
> hw rfkill switch. This results in hard-blocked radios after boot,
> resulting in always blocked radios rendering them unusable.
>
> The attached patch adds the ideapad
On Wed 08-03-17 09:23:40, Heiko Carstens wrote:
> On Tue, Mar 07, 2017 at 04:48:40PM +0100, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > __GFP_REPEAT has a rather weak semantic but since it has been introduced
> > around 2.6.12 it has been ignored for low order
On Wed 08-03-17 09:23:40, Heiko Carstens wrote:
> On Tue, Mar 07, 2017 at 04:48:40PM +0100, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > __GFP_REPEAT has a rather weak semantic but since it has been introduced
> > around 2.6.12 it has been ignored for low order allocations.
> >
> >
It looks like a bunch of devices do not like to be polled
for their reports at init time. When you look into the details,
it seems that for those that are requiring the quirk
HID_QUIRK_NO_INIT_REPORTS, the driver fails to retrieve part
of the features/inputs while others (more generic) work.
IMO,
It looks like a bunch of devices do not like to be polled
for their reports at init time. When you look into the details,
it seems that for those that are requiring the quirk
HID_QUIRK_NO_INIT_REPORTS, the driver fails to retrieve part
of the features/inputs while others (more generic) work.
IMO,
On Wed, Mar 08, 2017 at 01:55:59PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 20:07:25 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the
On Wed, Mar 08, 2017 at 01:55:59PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 20:07:25 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination
From: Markus Elfring
Date: Wed, 8 Mar 2017 08:45:31 +0100
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was
From: Markus Elfring
Date: Wed, 8 Mar 2017 08:45:31 +0100
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle
On Wed, Mar 08, 2017 at 01:50:59PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 19:40:31 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the
On Wed, Mar 08, 2017 at 01:50:59PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 19:40:31 +0100
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination
On Wed, Mar 08, 2017 at 01:48:46PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 19:25:55 +0100
>
> The local variables "req" and "rsp" will be set to appropriate pointers
> a bit later. Thus omit the explicit initialisations at the
On Wed, Mar 08, 2017 at 01:48:46PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 19:25:55 +0100
>
> The local variables "req" and "rsp" will be set to appropriate pointers
> a bit later. Thus omit the explicit initialisations at the beginning.
>
> Signed-off-by:
As per USB3.0 Specification "Table 9-20. Standard Endpoint Descriptor",
for interrupt and isochronous endpoints, wMaxPacketSize must be set to
1024 if the endpoint defines bMaxBurst to be greater than zero.
Signed-off-by: Roger Quadros
---
drivers/usb/gadget/function/f_uvc.c | 8
Hi Laurent & Felipe,
These are some fixes for SuperSpeed case.
--
cheers,
-roger
Roger Quadros (2):
usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's
wBytesPerInterval
usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed
drivers/usb/gadget/function/f_uvc.c | 10
As per USB3.0 Specification "Table 9-20. Standard Endpoint Descriptor",
for interrupt and isochronous endpoints, wMaxPacketSize must be set to
1024 if the endpoint defines bMaxBurst to be greater than zero.
Signed-off-by: Roger Quadros
---
drivers/usb/gadget/function/f_uvc.c | 8
1
Hi Laurent & Felipe,
These are some fixes for SuperSpeed case.
--
cheers,
-roger
Roger Quadros (2):
usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's
wBytesPerInterval
usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed
drivers/usb/gadget/function/f_uvc.c | 10
Hi,
On 08/03/17 09:54, Philipp Zabel wrote:
> Read back the register after setting or clearing a reset bit to make
> sure that the changes are applied to the reset controller hardware.
> Theoretically, this avoids the write to stay stuck in a store buffer
> during the delay of an
Hi,
On 08/03/17 09:54, Philipp Zabel wrote:
> Read back the register after setting or clearing a reset bit to make
> sure that the changes are applied to the reset controller hardware.
> Theoretically, this avoids the write to stay stuck in a store buffer
> during the delay of an
> On 03/06/2017 09:21 AM, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situations.
> >
>
> On 03/06/2017 09:21 AM, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situations.
> >
>
On Wed, Mar 08, 2017 at 01:41:00PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 18:23:54 +0100
>
> * Multiplications for the size determination of memory allocations
> indicated that array data structures should be processed.
>
On Wed, Mar 08, 2017 at 01:41:00PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 18:23:54 +0100
>
> * Multiplications for the size determination of memory allocations
> indicated that array data structures should be processed.
> Thus reuse the corresponding
On Wed, Mar 08 2017 at 1:28:13 pm GMT, "Michael S. Tsirkin"
wrote:
> On Wed, Mar 08, 2017 at 08:09:27AM +, Marc Zyngier wrote:
>> virtio-pci registers a per-vq affinity hint when using MSIX,
>> but fails to remove it when freeing the interrupt, resulting
>> in this type of
On Wed, Mar 08 2017 at 1:28:13 pm GMT, "Michael S. Tsirkin"
wrote:
> On Wed, Mar 08, 2017 at 08:09:27AM +, Marc Zyngier wrote:
>> virtio-pci registers a per-vq affinity hint when using MSIX,
>> but fails to remove it when freeing the interrupt, resulting
>> in this type of splat:
>>
>> [
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:10:50 +0100
Replace the specification of a data type by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:10:50 +0100
Replace the specification of a data type by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
On Tue, Mar 07, 2017 at 11:30:54PM +0100, Mats Karrman wrote:
> > > So, both the DP controller and the USB PD phy are I2C devices, and now I
> > > have to make them both
> > > attach to the AM bus as well?
> > The DP controller would provide the driver and the USB PD phy
> > (actually, the typec
On Tue, Mar 07, 2017 at 11:30:54PM +0100, Mats Karrman wrote:
> > > So, both the DP controller and the USB PD phy are I2C devices, and now I
> > > have to make them both
> > > attach to the AM bus as well?
> > The DP controller would provide the driver and the USB PD phy
> > (actually, the typec
On 2017-03-08 08:25, Richard Guy Briggs wrote:
> On 2017-03-07 14:23, Paul Moore wrote:
> > On Tue, Mar 7, 2017 at 1:44 PM, Paul Moore wrote:
> > > On Tue, Mar 7, 2017 at 10:55 AM, Richard Guy Briggs
> > > wrote:
> > >> On 2017-03-07 09:29, Paul Moore
On 2017-03-08 08:25, Richard Guy Briggs wrote:
> On 2017-03-07 14:23, Paul Moore wrote:
> > On Tue, Mar 7, 2017 at 1:44 PM, Paul Moore wrote:
> > > On Tue, Mar 7, 2017 at 10:55 AM, Richard Guy Briggs
> > > wrote:
> > >> On 2017-03-07 09:29, Paul Moore wrote:
> > >>> On Mon, Mar 6, 2017 at 11:03
Hi Magnus,
On Wed, Mar 8, 2017 at 12:02 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Tie in r8a7795 features and update the IOMMU_OF_DECLARE
> compat string to include the updated compat string.
>
> TODO:
> - Consider making use of
Hi Magnus,
On Wed, Mar 8, 2017 at 12:02 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Tie in r8a7795 features and update the IOMMU_OF_DECLARE
> compat string to include the updated compat string.
>
> TODO:
> - Consider making use of iommu_fwspec_add_ids() for uTLB handling
> Needed to
>>> +}
>>> +
>>> +static int p9_xen_write_todo(struct xen_9pfs_dataring *ring, RING_IDX size)
>>> +{
>>> + RING_IDX cons, prod;
>>> +
>>> + cons = ring->intf->out_cons;
>>> + prod = ring->intf->out_prod;
>>> + mb();
>>> +
>>> + if (XEN_9PFS_RING_SIZE - xen_9pfs_queued(prod, cons,
>>>
>>> +}
>>> +
>>> +static int p9_xen_write_todo(struct xen_9pfs_dataring *ring, RING_IDX size)
>>> +{
>>> + RING_IDX cons, prod;
>>> +
>>> + cons = ring->intf->out_cons;
>>> + prod = ring->intf->out_prod;
>>> + mb();
>>> +
>>> + if (XEN_9PFS_RING_SIZE - xen_9pfs_queued(prod, cons,
>>>
On Wed, Mar 8, 2017 at 8:25 AM, Richard Guy Briggs wrote:
> On 2017-03-07 14:23, Paul Moore wrote:
>> On Tue, Mar 7, 2017 at 1:44 PM, Paul Moore wrote:
>> > On Tue, Mar 7, 2017 at 10:55 AM, Richard Guy Briggs
>> > wrote:
>> >> On
On Mon 06-03-17 23:45:13, Kirill A. Shutemov wrote:
> Convert all non-architecture-specific code to 5-level paging.
>
> It's mostly mechanical adding handling one more page table level in
> places where we deal with pud_t.
>
> Signed-off-by: Kirill A. Shutemov
On Wed, Mar 8, 2017 at 8:25 AM, Richard Guy Briggs wrote:
> On 2017-03-07 14:23, Paul Moore wrote:
>> On Tue, Mar 7, 2017 at 1:44 PM, Paul Moore wrote:
>> > On Tue, Mar 7, 2017 at 10:55 AM, Richard Guy Briggs
>> > wrote:
>> >> On 2017-03-07 09:29, Paul Moore wrote:
>> >>> On Mon, Mar 6, 2017
On Mon 06-03-17 23:45:13, Kirill A. Shutemov wrote:
> Convert all non-architecture-specific code to 5-level paging.
>
> It's mostly mechanical adding handling one more page table level in
> places where we deal with pud_t.
>
> Signed-off-by: Kirill A. Shutemov
OK, I haven't spotted anything
Hi Magnus,
On Wed, Mar 8, 2017 at 12:02 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Hook up IOMMU_OF_DECLARE() support in case CONFIG_IOMMU_DMA
> is enabled. The only current supported case for 32-bit ARM
> is disabled, however for 64-bit
Hi Magnus,
On Wed, Mar 8, 2017 at 12:02 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Hook up IOMMU_OF_DECLARE() support in case CONFIG_IOMMU_DMA
> is enabled. The only current supported case for 32-bit ARM
> is disabled, however for 64-bit ARM usage of OF is required.
>
> Signed-off-by:
Hi Magnus,
On Wed, Mar 8, 2017 at 12:01 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Add root device handling to the IPMMU driver by allowing certain
> DT compat strings to enable has_cache_leaf_nodes that in turn will
> support both root
Hi Magnus,
On Wed, Mar 8, 2017 at 12:01 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> Add root device handling to the IPMMU driver by allowing certain
> DT compat strings to enable has_cache_leaf_nodes that in turn will
> support both root devices with interrupts and leaf devices that
> face
> On 03/06/2017 03:21 PM, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situations.
>
>
On Wed, Mar 08, 2017 at 01:45:43PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 19:09:20 +0100
>
> Replace the specification of data structures by references for variables
> as the parameter for the operator "sizeof" to make the
> On 03/06/2017 03:21 PM, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situations.
>
>
On Wed, Mar 08, 2017 at 01:45:43PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 7 Mar 2017 19:09:20 +0100
>
> Replace the specification of data structures by references for variables
> as the parameter for the operator "sizeof" to make the corresponding size
>
On Wed, Mar 08, 2017 at 06:17:50PM +0800, Baoquan He wrote:
> All right, I will just update the code comment. Just back ported kaslr
> to our OS product, people reviewed and found the upper boundary of kaslr
> mm region is EFI_VA_START, that's not correct, it has to be corrected
> firstly in
On Wed, Mar 08, 2017 at 06:17:50PM +0800, Baoquan He wrote:
> All right, I will just update the code comment. Just back ported kaslr
> to our OS product, people reviewed and found the upper boundary of kaslr
> mm region is EFI_VA_START, that's not correct, it has to be corrected
> firstly in
>
>>> + ring->bytes = (void*)__get_free_pages(GFP_KERNEL | __GFP_ZERO,
>>> XEN_9PFS_RING_ORDER);
>>> + if (ring->bytes == NULL)
>>> + goto error;
>>> + for (i = 0; i < (1 << XEN_9PFS_RING_ORDER); i++)
>>> + ring->intf->ref[i] =
>>>
>
>>> + ring->bytes = (void*)__get_free_pages(GFP_KERNEL | __GFP_ZERO,
>>> XEN_9PFS_RING_ORDER);
>>> + if (ring->bytes == NULL)
>>> + goto error;
>>> + for (i = 0; i < (1 << XEN_9PFS_RING_ORDER); i++)
>>> + ring->intf->ref[i] =
>>>
On 08/03/2017 at 13:33:33 +, Hadimani, Jagadish wrote:
> Hello Alexandre,
>
> I guess the Linux kernel uses HPET timer...
> But can we can force Linux kernel to use Tsc or per core timer...
>
That is probably the case but your are targeting the wrong subsystem.
The timekeeping is done using
On 08/03/2017 at 13:33:33 +, Hadimani, Jagadish wrote:
> Hello Alexandre,
>
> I guess the Linux kernel uses HPET timer...
> But can we can force Linux kernel to use Tsc or per core timer...
>
That is probably the case but your are targeting the wrong subsystem.
The timekeeping is done using
On Wed, 22 Feb 2017 02:06:29 +0200
Tuomas Tynkkynen wrote:
> Commit fd2421f54423 ("fs/9p: When doing inode lookup compare qid details
> and inode mode bits.") transformed v9fs_qid_iget() to use iget5_locked()
> instead of iget_locked(). However, the test() callback is not
On Wed, 22 Feb 2017 02:06:29 +0200
Tuomas Tynkkynen wrote:
> Commit fd2421f54423 ("fs/9p: When doing inode lookup compare qid details
> and inode mode bits.") transformed v9fs_qid_iget() to use iget5_locked()
> instead of iget_locked(). However, the test() callback is not checking
> fid.path at
From: Markus Elfring
Date: Wed, 8 Mar 2017 12:36:41 +0100
Do not use curly brackets at some source code places
where a single statement should be sufficient.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Tue, 7 Mar 2017 22:12:36 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style
From: Markus Elfring
Date: Wed, 8 Mar 2017 12:36:41 +0100
Do not use curly brackets at some source code places
where a single statement should be sufficient.
Signed-off-by: Markus Elfring
---
drivers/infiniband/hw/ocrdma/ocrdma_verbs.c | 41 +++--
1 file changed, 16
From: Markus Elfring
Date: Tue, 7 Mar 2017 22:12:36 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by:
On Wed, Mar 08, 2017 at 02:27:05PM +0100, Jiri Kosina wrote:
> From: Jiri Kosina
>
> klp_mutex is shared between core.c and transition.c, and as such would
> rather be properly located in a header so that we don't have to play
> 'extern' games from .c sources.
>
> This also
On Wed, Mar 08, 2017 at 02:27:05PM +0100, Jiri Kosina wrote:
> From: Jiri Kosina
>
> klp_mutex is shared between core.c and transition.c, and as such would
> rather be properly located in a header so that we don't have to play
> 'extern' games from .c sources.
>
> This also silences sparse
On 07/03/17 03:17, Magnus Damm wrote:
> From: Magnus Damm
>
> Introduce an alternative set of iommu_ops suitable for 64-bit ARM
> as well as 32-bit ARM when CONFIG_IOMMU_DMA=y. Also adjust the
> Kconfig to depend on ARM or IOMMU_DMA. Initialize the device
> from
On 07/03/17 03:17, Magnus Damm wrote:
> From: Magnus Damm
>
> Introduce an alternative set of iommu_ops suitable for 64-bit ARM
> as well as 32-bit ARM when CONFIG_IOMMU_DMA=y. Also adjust the
> Kconfig to depend on ARM or IOMMU_DMA. Initialize the device
> from ->xlate() when
From: Markus Elfring
Date: Wed, 8 Mar 2017 11:11:35 +0100
This issue was detected by using the Coccinelle software.
1. Return directly if a call of the function "_ocrdma_alloc_pd" failed.
2. Reduce the scope for the local variable "status" to one case
of an if
From: Markus Elfring
Date: Wed, 8 Mar 2017 11:11:35 +0100
This issue was detected by using the Coccinelle software.
1. Return directly if a call of the function "_ocrdma_alloc_pd" failed.
2. Reduce the scope for the local variable "status" to one case
of an if statement.
3. Delete the jump
On Fri, 2016-11-11 at 07:08 -0500, Felix Janda wrote:
> Currently, libc-compat.h detects inclusion of specific glibc headers,
> and defines corresponding _UAPI_DEF_* macros, which in turn are used in
> uapi headers to prevent definition of conflicting structures/constants.
> There is no such
On Fri, 2016-11-11 at 07:08 -0500, Felix Janda wrote:
> Currently, libc-compat.h detects inclusion of specific glibc headers,
> and defines corresponding _UAPI_DEF_* macros, which in turn are used in
> uapi headers to prevent definition of conflicting structures/constants.
> There is no such
On Wed, 8 Mar 2017, Jiri Kosina wrote:
> From: Jiri Kosina
>
> klp_mutex is shared between core.c and transition.c, and as such would
> rather be properly located in a header so that we don't have to play
> 'extern' games from .c sources.
>
> This also silences sparse
On Wed, 8 Mar 2017, Jiri Kosina wrote:
> From: Jiri Kosina
>
> klp_mutex is shared between core.c and transition.c, and as such would
> rather be properly located in a header so that we don't have to play
> 'extern' games from .c sources.
>
> This also silences sparse warning (wrongly)
From: Markus Elfring
Date: Tue, 7 Mar 2017 22:23:17 +0100
Omit an extra message for a memory allocation failure in this function.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
Signed-off-by: Markus Elfring
From: Markus Elfring
Date: Tue, 7 Mar 2017 22:23:17 +0100
Omit an extra message for a memory allocation failure in this function.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:00:41 +0100
Delete an assignment for the local variable "status" in an if branch
because the desired failure indication is already specified by a constant
error code at the end.
Signed-off-by: Markus Elfring
On Wed, Mar 08, 2017 at 08:09:27AM +, Marc Zyngier wrote:
> virtio-pci registers a per-vq affinity hint when using MSIX,
> but fails to remove it when freeing the interrupt, resulting
> in this type of splat:
>
> [ 31.111202] WARNING: CPU: 0 PID: 2823 at kernel/irq/manage.c:1503
>
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:58:34 +0100
1. Return zero in one case directly.
2. Return the value from a call of the function "_ocrdma_dealloc_pd"
without using an extra assignment for the local variable.
3. Remove the variable "status" in
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:00:41 +0100
Delete an assignment for the local variable "status" in an if branch
because the desired failure indication is already specified by a constant
error code at the end.
Signed-off-by: Markus Elfring
---
On Wed, Mar 08, 2017 at 08:09:27AM +, Marc Zyngier wrote:
> virtio-pci registers a per-vq affinity hint when using MSIX,
> but fails to remove it when freeing the interrupt, resulting
> in this type of splat:
>
> [ 31.111202] WARNING: CPU: 0 PID: 2823 at kernel/irq/manage.c:1503
>
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:58:34 +0100
1. Return zero in one case directly.
2. Return the value from a call of the function "_ocrdma_dealloc_pd"
without using an extra assignment for the local variable.
3. Remove the variable "status" in this function then.
Hi,
On 07/03/2017 at 00:48:18 +0530, Shah, Nehal-bakulchandra wrote:
> Hi,
>
> Currently we are having hardware which does not have RTC. It is single
> processor system. However it does have TSC timer.
>
> Now, how to use scheduler with only TSC as current kernel scheduler leverage
> the RTC
Hi,
On 07/03/2017 at 00:48:18 +0530, Shah, Nehal-bakulchandra wrote:
> Hi,
>
> Currently we are having hardware which does not have RTC. It is single
> processor system. However it does have TSC timer.
>
> Now, how to use scheduler with only TSC as current kernel scheduler leverage
> the RTC
From: Jiri Kosina
klp_mutex is shared between core.c and transition.c, and as such would
rather be properly located in a header so that we don't have to play
'extern' games from .c sources.
This also silences sparse warning (wrongly) suggesting that klp_mutex
should be
From: Jiri Kosina
klp_mutex is shared between core.c and transition.c, and as such would
rather be properly located in a header so that we don't have to play
'extern' games from .c sources.
This also silences sparse warning (wrongly) suggesting that klp_mutex
should be defined static.
Hi Ramiro,
On Tue, Mar 07, 2017 at 02:37:50PM +, Ramiro Oliveira wrote:
> Create device tree bindings documentation for the CSI-2 Host Video
> platform.
Extra space here.
>
> Signed-off-by: Ramiro Oliveira
> ---
> .../devicetree/bindings/media/snps,plat-csi2.txt
Hi Ramiro,
On Tue, Mar 07, 2017 at 02:37:50PM +, Ramiro Oliveira wrote:
> Create device tree bindings documentation for the CSI-2 Host Video
> platform.
Extra space here.
>
> Signed-off-by: Ramiro Oliveira
> ---
> .../devicetree/bindings/media/snps,plat-csi2.txt | 77
>
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:48:24 +0100
Return constant integer values without storing them in the local
variable "status".
Signed-off-by: Markus Elfring
---
drivers/infiniband/hw/ocrdma/ocrdma_verbs.c | 9
From: Markus Elfring
Date: Wed, 8 Mar 2017 10:48:24 +0100
Return constant integer values without storing them in the local
variable "status".
Signed-off-by: Markus Elfring
---
drivers/infiniband/hw/ocrdma/ocrdma_verbs.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff
From: Markus Elfring
Date: Wed, 8 Mar 2017 09:19:47 +0100
* Multiplications for the size determination of memory allocations
indicated that array data structures should be processed.
Thus reuse the corresponding function "kcalloc".
This issue was detected by
From: Markus Elfring
Date: Wed, 8 Mar 2017 09:19:47 +0100
* Multiplications for the size determination of memory allocations
indicated that array data structures should be processed.
Thus reuse the corresponding function "kcalloc".
This issue was detected by using the Coccinelle software.
Comparing a size_t with less than zero is always false as size_t
is unsigned. So, change the type of the variable to ssize_t and
replicate the size check from mux_configure_channel() into
mux_write_ext_info() thus ensuring that the size will fit in the
ssize_t variable.
Detected by CoverityScan,
Comparing a size_t with less than zero is always false as size_t
is unsigned. So, change the type of the variable to ssize_t and
replicate the size check from mux_configure_channel() into
mux_write_ext_info() thus ensuring that the size will fit in the
ssize_t variable.
Detected by CoverityScan,
On 2017-03-07 14:23, Paul Moore wrote:
> On Tue, Mar 7, 2017 at 1:44 PM, Paul Moore wrote:
> > On Tue, Mar 7, 2017 at 10:55 AM, Richard Guy Briggs wrote:
> >> On 2017-03-07 09:29, Paul Moore wrote:
> >>> On Mon, Mar 6, 2017 at 11:03 PM, Richard Guy Briggs
On 2017-03-07 14:23, Paul Moore wrote:
> On Tue, Mar 7, 2017 at 1:44 PM, Paul Moore wrote:
> > On Tue, Mar 7, 2017 at 10:55 AM, Richard Guy Briggs wrote:
> >> On 2017-03-07 09:29, Paul Moore wrote:
> >>> On Mon, Mar 6, 2017 at 11:03 PM, Richard Guy Briggs
> >>> wrote:
> >>> > On 2017-03-06
CDM nodes need a way of explicit memory allocation mechanism from the user
space. After the previous FALLBACK zonelist rebuilding process changes, the
mbind(MPOL_BIND) based allocation request fails on the CDM node. This is
because allocation requesting local node's FALLBACK zonelist is selected
CDM nodes need a way of explicit memory allocation mechanism from the user
space. After the previous FALLBACK zonelist rebuilding process changes, the
mbind(MPOL_BIND) based allocation request fails on the CDM node. This is
because allocation requesting local node's FALLBACK zonelist is selected
From: Markus Elfring
Date: Tue, 7 Mar 2017 19:25:55 +0100
The local variables "req" and "rsp" will be set to appropriate pointers
a bit later. Thus omit the explicit initialisations at the beginning.
Signed-off-by: Markus Elfring
From: Markus Elfring
Date: Tue, 7 Mar 2017 19:25:55 +0100
The local variables "req" and "rsp" will be set to appropriate pointers
a bit later. Thus omit the explicit initialisations at the beginning.
Signed-off-by: Markus Elfring
---
drivers/infiniband/hw/ocrdma/ocrdma_hw.c | 5 ++---
1 file
1101 - 1200 of 1714 matches
Mail list logo