On Mon, Aug 12, 2024 at 08:48:16AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 12.08.24 um 08:42 schrieb Dan Carpenter:
> > This code has an issue because it loops until "i" is set to UINT_MAX but
> > the test for failure assumes that "i" is set to zero. The result is that
> > it will only print
On Mon, Aug 12, 2024 at 09:42:53AM +0300, Dan Carpenter wrote:
> This code has an issue because it loops until "i" is set to UINT_MAX but
> the test for failure assumes that "i" is set to zero. The result is that
> it will only print an error message if we succeed on the very last try.
> Reformat
Hi
Am 12.08.24 um 08:42 schrieb Dan Carpenter:
This code has an issue because it loops until "i" is set to UINT_MAX but
the test for failure assumes that "i" is set to zero. The result is that
it will only print an error message if we succeed on the very last try.
Reformat the loop to count for
This code has an issue because it loops until "i" is set to UINT_MAX but
the test for failure assumes that "i" is set to zero. The result is that
it will only print an error message if we succeed on the very last try.
Reformat the loop to count forwards instead of backwards.
Fixes: 2281475168d2 (
On 12/08/2024 05:00, Hui-Ping Chen wrote:
> Nuvoton MA35 SoCs NAND Flash Interface Controller
> supports 2KB, 4KB and 8KB page size, and up to 8-bit,
> 12-bit, and 24-bit hardware ECC calculation circuit
> to protect data communication.
>
> Signed-off-by: Hui-Ping Chen
> ---
> drivers/mtd/nand/r
On 12/08/2024 05:00, Hui-Ping Chen wrote:
> Add dt-bindings for the Nuvoton MA35 SoC NAND Controller.
>
> Signed-off-by: Hui-Ping Chen
> ---
> .../bindings/mtd/nuvoton,ma35d1-nand.yaml | 97 +++
> 1 file changed, 97 insertions(+)
> create mode 100644
> Documentation/devicet
Add support for the drm_panic module, which displays a pretty user
friendly message on the screen when a Linux kernel panic occurs.
Signed-off-by: Lu Yao
---
Changes in v2:
1. Drop include "drm_internal.h"
2. Add disabling DC tiling ops.
Per suggestion from previous thread:
https://patchwork.fre
On 10-08-2024 03:58, Matthew Brost wrote:
Avoid leaking a lockdep map on each drm sched creation and destruction
by using a single lockdep map for all drm sched allocated submit_wq.
v2:
- Use alloc_ordered_workqueue_lockdep_map (Tejun)
Cc: Luben Tuikov
Cc: Christian König
Signed-off-by:
Hi
Am 09.08.24 um 19:06 schrieb Dan Carpenter:
On Fri, Aug 09, 2024 at 04:43:51PM +0300, Jani Nikula wrote:
On Fri, 09 Aug 2024, Thomas Zimmermann wrote:
Hi,
thanks a lot for the bugfix.
Am 09.08.24 um 14:33 schrieb Dan Carpenter:
The test for "Link training failed" expect the loop to exit
On 10-08-2024 03:58, Matthew Brost wrote:
Add an interface for a user-defined workqueue lockdep map, which is
helpful when multiple workqueues are created for the same purpose. This
also helps avoid leaking lockdep maps on each workqueue creation.
v2:
- Add alloc_workqueue_lockdep_map (Teju
在 2024/8/10 9:28, Kasireddy, Vivek 写道:
[Some people who received this message don't often get email from
vivek.kasire...@intel.com. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
Hi Huan,
The current udmabuf mmap uses a page fault mechanism to populate the
v
在 2024/8/10 10:52, Kasireddy, Vivek 写道:
[Some people who received this message don't often get email from
vivek.kasire...@intel.com. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
Hi Huan,
Currently, udmabuf handles folio by creating an unpin list to record
在 2024/8/10 10:39, Kasireddy, Vivek 写道:
[Some people who received this message don't often get email from
vivek.kasire...@intel.com. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
Hi Huan,
Currently vmap_udmabuf set page's array by each folio.
But, ubuf->fol
在 2024/8/10 9:29, Kasireddy, Vivek 写道:
[Some people who received this message don't often get email from
vivek.kasire...@intel.com. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
Hi Huan,
When PAGE_SIZE 4096, MAX_PAGE_ORDER 10, 64bit machine,
page_alloc only
To prevent erros from occurring when the src string is longer than the
dst string in strcpy(), we should use strscpy() instead. This
approach also facilitates future extensions to the task comm.
Signed-off-by: Yafang Shao
Acked-by: Daniel Vetter
Cc: Maarten Lankhorst
Cc: Maxime Ripard
Cc: Thom
To prevent errors from occurring when the src string is longer than the dst
string in strcpy(), we should use strscpy() instead. This approach
also facilitates future extensions to the task comm.
Signed-off-by: Yafang Shao
Cc: "David S. Miller"
Cc: David Ahern
Cc: Eric Dumazet
Cc: Jakub Kicins
Using strscpy() to read the task comm ensures that the name is
always NUL-terminated, regardless of the source string. This approach also
facilitates future extensions to the task comm.
Signed-off-by: Yafang Shao
Acked-by: Masami Hiramatsu (Google)
Cc: Steven Rostedt
Cc: Mathieu Desnoyers
---
These three functions follow the same pattern. To deduplicate the code,
let's introduce a common helper __kmemdup_nul().
Suggested-by: Andrew Morton
Signed-off-by: Yafang Shao
Cc: Simon Horman
Cc: Matthew Wilcox
---
mm/util.c | 67 +--
1 fil
In kstrdup(), it is critical to ensure that the dest string is always
NUL-terminated. However, potential race condidtion can occur between a
writer and a reader.
Consider the following scenario involving task->comm:
readerwriter
len = strlen(s) + 1;
Let's explicitly ensure the destination string is NUL-terminated. This way,
it won't be affected by changes to the source string.
Signed-off-by: Yafang Shao
Reviewed-by: Quentin Monnet
---
tools/bpf/bpftool/pids.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/bpf/bpftool/pids.c b/
Quoted from Linus [0]:
selinux never wanted a lock, and never wanted any kind of *consistent*
result, it just wanted a *stable* result.
Using get_task_comm() to read the task comm ensures that the name is
always NUL-terminated, regardless of the source string. This approach also
facilitates f
Using strscpy() to read the task comm ensures that the name is
always NUL-terminated, regardless of the source string. This approach also
facilitates future extensions to the task comm.
Signed-off-by: Yafang Shao
Acked-by: Paul Moore
Cc: Eric Paris
---
kernel/auditsc.c | 6 +++---
1 file chang
We want to eliminate the use of __get_task_comm() for the following
reasons:
- The task_lock() is unnecessary
Quoted from Linus [0]:
: Since user space can randomly change their names anyway, using locking
: was always wrong for readers (for writers it probably does make sense
: to have so
Using {memcpy,strncpy,strcpy,kstrdup} to copy the task comm relies on the
length of task comm. Changes in the task comm could result in a destination
string that is overflow. Therefore, we should explicitly ensure the
destination string is always NUL-terminated, regardless of the task comm.
This ap
Hi Cristian,
At 2024-08-08 19:58:02, "Cristian Ciocaltea"
wrote:
>Move rockchip_drm_platform_driver unregistration after its sub-drivers,
>which ensures all drivers are unregistered in the reverse order used
>when they were registered.
Would you please provied some detail information about how
On Thu, Aug 8, 2024 at 13:24 PM Alex Deucher wrote:
>
> On Thu, Aug 8, 2024 at 12:43 PM Alex Deucher wrote:
> >
> > On Thu, Aug 8, 2024 at 2:35 AM Lu Yao wrote:
> > >
> > > On 2024/8/5 17:25, Jocelyn Falempe wrote:
> > > >
> > > >
> > > > On 02/08/2024 11:39, Christian König wrote:
> > > >> Am 0
On 8/11/24 03:21, Mina Almasry wrote:
On Fri, Aug 9, 2024 at 11:52 PM Jakub Kicinski wrote:
On Fri, 9 Aug 2024 16:45:50 +0100 Pavel Begunkov wrote:
I think this is good, and it doesn't seem hacky to me, because we can
check the page_pools of the netdev while we hold rtnl, so we can be
sure no
Hi Morimoto-san,
(CC'ing Sakari)
Thank you for the patch.
On Fri, Aug 09, 2024 at 04:22:22AM +, Kuninori Morimoto wrote:
> We have endpoint base functions
> - of_graph_get_next_device_endpoint()
> - of_graph_get_device_endpoint_count()
> - for_each_of_graph_device_endpoint(
This patch takes care of the following warnings during documentation
compiling:
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
'width' not described in 'drm_plane_size_hint'
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
'height'
On Tue, Jul 30, 2024 at 08:53:39PM +0200, Kevin Holm wrote:
> From: Wayne Lin
>
> [ Upstream commit fa57924c76d995e87ca3533ec60d1d5e55769a27 ]
>
> [Why]
> dm_dp_mst_is_port_support_mode() is a bit not following the original design
> rule and cause
> light up issue with multiple 4k monitors afte
On Mon, 29 Jul 2024, at 12:47 AM, Bouke Sybren Haarsma wrote:
> Add quirk orientation for Ayn Loki Max model.
>
> This has been tested by JELOS team that uses their
> own patched kernel for a while now and confirmed by
> users in the ChimeraOS discord servers.
>
> Signed-off-by: Bouke Sybren Haar
---
Spelling errors fixed: successe, inistilize, and ddestroy.
drivers/gpu/drm/ttm/ttm_pool.c | 2 +-
drivers/gpu/drm/ttm/ttm_resource.c | 2 +-
include/drm/ttm/ttm_device.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_pool.c b/drivers/g
Some new Rogue GPU cores have an extra MARS power domain, which
controlls the power of the firmware core and allows the firmware core to
power down most parts of the GPU.
Adapt to this by ignoring power domains that should be powered down by
the fiwmare and checking MARS idle status instead.
The
38 matches
Mail list logo
