From: Davidlohr Bueso <dave@stgolabs.net>
To: Simon Horman <horms@kernel.org>
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
kuba@kernel.org, pabeni@redhat.com, anisa.su@samsung.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mctp: accept MSG_CMSG_COMPAT in recvmsg
Date: Thu, 5 Nov 2026 07:32:39 -0800 [thread overview]
Message-ID: <20261105153239.qmqroxth43ncnln5@offworld> (raw)
In-Reply-To: <20261105135808.GS865646@horms.kernel.org>
On Thu, 05 Nov 2026, Simon Horman wrote:
>On Sun, Nov 01, 2026 at 12:03:31PM -0800, Davidlohr Bueso wrote:
>> 32-bit userspace running on a 64-bit kernel is unable to receive MCTP
>> messages on an AF_MCTP socket, even though sending succeeds. There is
>> nothing for MCTP to do with it beyond not rejecting it, as af_packet,
>> af_key and can/isotp already do, for example.
>
>Hi Davidlohr,
>
>Thanks for your patch.
>
>As prompted elsewhere by a bot, it would be good if the patch description
>included some information about how this was found. And also to what
>extent the fix has been tested. I know you answered that already but
>I'm going to ask for a v2 for other reasons. And it would be good
>to include that detail there.
Thanks for taking a look.
So I don't think the changelog should be mentioning random userspace
programs for testing/verifying this - as the bot email suggested, just
replying there should be enough.
>
>>
>> Fixes: 833ef3b91de6 ("mctp: Populate socket implementation")
>> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
>
>This seems to be a fix that effects users. Which I believe you have
>reproduced. As such I'd lean towards this being for net, CCed to stable.
>
>Subject: [PATCH net v2] ...
>
>Otherwise, it should be for net-next.
>
>Subject: [PATCH net-next v2] ...
Will do.
>
>> ---
>> net/mctp/af_mctp.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/mctp/af_mctp.c b/net/mctp/af_mctp.c
>> index 8af5e2b3c8d1..aa22c0860712 100644
>> --- a/net/mctp/af_mctp.c
>> +++ b/net/mctp/af_mctp.c
>> @@ -292,8 +292,7 @@ static int mctp_recvmsg(struct socket *sock, struct msghdr *msg, size_t len,
>
>Strangely this patch has been mangled - the original code is 7 rather than
>8 lines long. (s/,8/,7). Because of this it could not be applied by our
>CI which then did not run the usual tests.
Yeah I messed that up (noticed sashiko couldn't apply it either), not
sure what happened.
Thanks,
Davidlohr
prev parent reply other threads:[~2026-11-05 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 20:03 Davidlohr Bueso
2026-11-01 20:09 ` netdev-bot+sinfo
2026-11-01 20:41 ` Davidlohr Bueso
2026-11-05 13:58 ` Simon Horman
2026-11-05 15:32 ` Davidlohr Bueso [this message]
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=20261105153239.qmqroxth43ncnln5@offworld \
--to=dave@stgolabs.net \
--cc=anisa.su@samsung.com \
--cc=horms@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®