All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, cleger@rivosinc.com
Subject: Re: [PATCH] riscv: uaccess: fix __put_user_nocheck for unaligned accesses
Date: Wed, 06 Aug 2025 17:15:49 +0000	[thread overview]
Message-ID: <175450054925.2863135.866620119887163563.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724220853.1969954-1-aurelien@aurel32.net>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:

On Fri, 25 Jul 2025 00:08:52 +0200 you wrote:
> The type of the value to write should be determined by the size of the
> destination, not by the value itself, which may be a constant. This
> aligns the behavior with x86_64, where __typeof__(*(__gu_ptr)) is used
> to infer the correct type.
> 
> This fixes an issue in put_cmsg, which was only writing 4 out of 8
> bytes to the cmsg_len field, causing the glibc tst-socket-timestamp test
> to fail.
> 
> [...]

Here is the summary with links:
  - riscv: uaccess: fix __put_user_nocheck for unaligned accesses
    https://git.kernel.org/riscv/c/a10ce19d93c9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, cleger@rivosinc.com
Subject: Re: [PATCH] riscv: uaccess: fix __put_user_nocheck for unaligned accesses
Date: Wed, 06 Aug 2025 17:15:49 +0000	[thread overview]
Message-ID: <175450054925.2863135.866620119887163563.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724220853.1969954-1-aurelien@aurel32.net>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:

On Fri, 25 Jul 2025 00:08:52 +0200 you wrote:
> The type of the value to write should be determined by the size of the
> destination, not by the value itself, which may be a constant. This
> aligns the behavior with x86_64, where __typeof__(*(__gu_ptr)) is used
> to infer the correct type.
> 
> This fixes an issue in put_cmsg, which was only writing 4 out of 8
> bytes to the cmsg_len field, causing the glibc tst-socket-timestamp test
> to fail.
> 
> [...]

Here is the summary with links:
  - riscv: uaccess: fix __put_user_nocheck for unaligned accesses
    https://git.kernel.org/riscv/c/a10ce19d93c9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-08-06 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 22:08 [PATCH] riscv: uaccess: fix __put_user_nocheck for unaligned accesses Aurelien Jarno
2025-07-24 22:08 ` Aurelien Jarno
2025-07-25 13:42 ` Alexandre Ghiti
2025-07-25 13:42   ` Alexandre Ghiti
2025-08-06 17:15 ` patchwork-bot+linux-riscv [this message]
2025-08-06 17:15   ` patchwork-bot+linux-riscv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=175450054925.2863135.866620119887163563.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=aurelien@aurel32.net \
    --cc=cleger@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.