linux-kernel - Re: [PATCH] mailbox: Allow NULL message sending

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABb+yY25mpUQjW7N-+uYWZ9s4xYLpvV00S9CJigtiO7wa_EGnQ@mail.gmail.com>
Date: Wed, 3 Dec 2025 20:08:28 -0600
From: Jassi Brar <jassisinghbrar@...il.com>
To: Joonwon Kang <joonwonkang@...gle.com>
Cc: sudeep.holla@....com, thierry.reding@...il.com, jonathanh@...dia.com, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mailbox: Allow NULL message sending

On Tue, Nov 25, 2025 at 11:00 PM Joonwon Kang <joonwonkang@...gle.com> wrote:
>
> Clients may want to send interrupt only without any useful message
> involved. Since the current mailbox framework does not allow NULL
> message sending(although it allows receiving it), the clients should
> allocate a dummy message buffer and pretend sending it. Besides, if
> the mailbox controller calls `mbox_chan_txdone()` when the client
> drivers happen to send NULL message anyway, it will result in unexpected
> results by making the tx status messed up. This commit lifts the
> limitation and allows the clients to send interrupt only without any
> message buffer allocated.
>
Interrupts without data messages are called 'doorbells' and we already
support them.
thanks