similar to: [PATCH 04/18] nouveau: change strncpy+truncation to strlcpy

(added various kvm/virtualization lists in Cc as well as qemu as I don't know who's "wrong" here) Pavel Tatashin wrote on Thu, Jul 19, 2018: > Allow sched_clock() to be used before schec_clock_init() is called. > This provides with a way to get early boot timestamps on machines with > unstable clocks. This isn't something I understand, but bisect tells me this

Hi Dominique, On 08/22/2014 02:27 AM, Dominique Martinet wrote: > Hi, > > Christopher Covington wrote on Thu, Aug 21, 2014 at 03:50:58PM -0400: >> With my 3.15.0+ kernel, qemu-system-x86_64 substituted for qemu-kvm, and the >> path changed from your arguments I get: >> >> 9pnet_virtio: no channels available >> VFS: Cannot open root device "root"

From: Xiongfeng Wang <xiongfeng.wang at linaro.org> gcc-8 reports drivers/gpu/drm/nouveau/nvif/client.c: In function 'nvif_client_init': ./include/linux/string.h:245:9: warning: '__builtin_strncpy' specified bound 32 equals destination size [-Wstringop-truncation] We need to use strlcpy() to make sure the dest string is nul-terminated. Signed-off-by: Xiongfeng Wang

... and demote non-conformant kernel-doc header. Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/core/firmware.c:71: warning: Function parameter or member 'subdev' not described in 'nvkm_firmware_get' drivers/gpu/drm/nouveau/nvkm/core/firmware.c:71: warning: Function parameter or member 'fwname' not described in 'nvkm_firmware_get'

Add two functions nvkm_firmware_get() and nvkm_firmware_put() to load a firmware file and free its resources, respectively. Since firmware files are becoming a necessity for new GPUs, and their location has been standardized to nvidia/chip/, this will prevent duplicate and error-prone name-generation code. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> ---

Hi Michael, Albert, Albert Huang wrote on Sat, Mar 25, 2023 at 06:56:33PM +0800: > in virtio_net, if we disable the napi_tx, when we triger a tx interrupt, > the vq->event_triggered will be set to true. It will no longer be set to > false. Unless we explicitly call virtqueue_enable_cb_delayed or > virtqueue_enable_cb_prepare. This patch (commited as 35395770f803

On Thu, Jan 21, 2016 at 8:41 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote: > Hi Alexandre, > > On 18 January 2016 at 06:07, Alexandre Courbot <acourbot at nvidia.com> wrote: >> Add two functions nvkm_firmware_get() and nvkm_firmware_put() to load a >> firmware file and free its resources, respectively. Since firmware files >> are becoming a necessity

On Fri, Nov 04, 2016 at 06:36:17PM +0900, Alexandre Courbot wrote: > Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path > if they cannot be found in the new, "official" path. User setups were > broken by the switch, which is bad. > > There are only 4 firmware files we may want to look up that way, so > hardcode them into the lookup

On Wed, Nov 2, 2016 at 12:54 AM, Alexandre Courbot <acourbot at nvidia.com> wrote: > Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path > if they cannot be found in the new, "official" path. User setups were > broken by the switch, which is bad. > > There are only 4 firmware files we may want to look up that way, so > hardcode them

On 11/02/2016 03:52 PM, Alexandre Courbot wrote: > On 11/02/2016 02:07 PM, Ilia Mirkin wrote: >> On Wed, Nov 2, 2016 at 12:54 AM, Alexandre Courbot <acourbot at nvidia.com> wrote: >>> Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path >>> if they cannot be found in the new, "official" path. User setups were >>>

Hi Alexandre, On 18 January 2016 at 06:07, Alexandre Courbot <acourbot at nvidia.com> wrote: > Add two functions nvkm_firmware_get() and nvkm_firmware_put() to load a > firmware file and free its resources, respectively. Since firmware files > are becoming a necessity for new GPUs, and their location has been > standardized to nvidia/chip/, this will prevent duplicate and >

Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path if they cannot be found in the new, "official" path. User setups were broken by the switch, which is bad. There are only 4 firmware files we may want to look up that way, so hardcode them into the lookup function. All new firmware files should use the standard "nvidia/<chip>/gr/" path.

Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path if they cannot be found in the new, "official" path. User setups were broken by the switch, which is bad. There are only 4 firmware files we may want to look up that way, so hardcode them into the lookup function. All new firmware files should use the standard "nvidia/<chip>/gr/" path.

On 11/02/2016 02:07 PM, Ilia Mirkin wrote: > On Wed, Nov 2, 2016 at 12:54 AM, Alexandre Courbot <acourbot at nvidia.com> wrote: >> Look for firmware files using the legacy ("nouveau/nvxx_fucxxxx") path >> if they cannot be found in the new, "official" path. User setups were >> broken by the switch, which is bad. >> >> There are only 4

Call strtolower() rather than walking the string explicitly to convert it to lowercase. Signed-off-by: Markus Mayer <mmayer at broadcom.com> --- drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/core/firmware.c b/drivers/gpu/drm/nouveau/nvkm/core/firmware.c index 34ecd4a..c50594c 100644 ---

Hi Dominique, On 08/22/2014 08:49 AM, Dominique Martinet wrote: > Hi, > > Christopher Covington wrote on Fri, Aug 22, 2014 at 08:37:52AM -0400: >> Thanks for the pointer to this patch. I think I started this kernel half way >> through the 3.16 merge window. The last non-cherry-picked patch I have is: >> >> commit 6d87c225f5d82d29243dc124f1ffcbb0e14ec358 >>

On Sun, Jul 3, 2016 at 12:21 AM, Markus Mayer <markus.mayer at broadcom.com> wrote: > On 1 July 2016 at 18:18, Alexandre Courbot <gnurou at gmail.com> wrote: >> On Fri, Jul 1, 2016 at 8:50 AM, Markus Mayer <mmayer at broadcom.com> wrote: >>> Call strtolower() rather than walking the string explicitly to convert >>> it to lowercase. >>>

On 1 July 2016 at 18:18, Alexandre Courbot <gnurou at gmail.com> wrote: > On Fri, Jul 1, 2016 at 8:50 AM, Markus Mayer <mmayer at broadcom.com> wrote: >> Call strtolower() rather than walking the string explicitly to convert >> it to lowercase. >> >> Signed-off-by: Markus Mayer <mmayer at broadcom.com> >> --- >>

On Fri, Jul 1, 2016 at 8:50 AM, Markus Mayer <mmayer at broadcom.com> wrote: > Call strtolower() rather than walking the string explicitly to convert > it to lowercase. > > Signed-off-by: Markus Mayer <mmayer at broadcom.com> > --- > drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 7 +------ > 1 file changed, 1 insertion(+), 6 deletions(-) > > diff --git

Just another udev segfault. strlcpy() writes behind the specified maximum size. strlcat() causes the same probelem and truncates the destination string to the maximum size which isn't the job for a concatenation function. Thanks, Kay diff -Nru a/klibc/klibc/strlcat.c b/klibc/klibc/strlcat.c --- a/klibc/klibc/strlcat.c 2005-03-27 04:40:42 +02:00 +++ b/klibc/klibc/strlcat.c 2005-03-27