All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: "Kees Cook" <kees@kernel.org>,
	"Rusty Russell" <rusty@rustcorp.com.au>,
	"Petr Pavlu" <petr.pavlu@suse.com>,
	"Daniel Gomez" <da.gomez@kernel.org>,
	"Sami Tolvanen" <samitolvanen@google.com>,
	linux-modules@vger.kernel.org,
	"Hans Verkuil" <hverkuil+cisco@kernel.org>,
	"Malcolm Priestley" <tvboxspy@gmail.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Hans Verkuil" <hverkuil@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-hardening@vger.kernel.org,
	"Luis Chamberlain" <mcgrof@kernel.org>,
	"Chris Li" <sparse@chrisli.org>,
	linux-sparse@vger.kernel.org
Subject: Re: [PATCH v2 3/3] module: Add compile-time check for embedded NUL characters
Date: Fri, 19 Dec 2025 15:44:06 +0300	[thread overview]
Message-ID: <aUVIlvOSvobrdrKV@stanley.mountain> (raw)
In-Reply-To: <47a2f0c7-c25f-4734-840b-fdefc2f3c4a9@kernel.org>

On Fri, Dec 19, 2025 at 01:29:21PM +0100, Matthieu Baerts wrote:
> net/mptcp/crypto_test.c:72:1: error: bad integer constant expression
> net/mptcp/crypto_test.c:72:1: error: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
> net/mptcp/crypto_test.c:73:1: error: bad integer constant expression
> net/mptcp/crypto_test.c:73:1: error: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"

There was a fix for that posted.  Let me ping them to see if anyone is
planning to send an actual patch.

https://lore.kernel.org/all/20251211175101.GA3405942@google.com/

regards
dan carpenter


  parent reply	other threads:[~2025-12-19 12:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10  3:06 [PATCH v2 0/3] module: Add compile-time check for embedded NUL characters Kees Cook
2025-10-10  3:06 ` [PATCH v2 1/3] media: dvb-usb-v2: lmedm04: Fix firmware macro definitions Kees Cook
2025-10-10  7:10   ` Mauro Carvalho Chehab
2025-10-10  3:06 ` [PATCH v2 2/3] media: radio: si470x: Fix DRIVER_AUTHOR macro definition Kees Cook
2025-10-10  7:10   ` Mauro Carvalho Chehab
2025-10-10  3:06 ` [PATCH v2 3/3] module: Add compile-time check for embedded NUL characters Kees Cook
2025-10-10  4:19   ` Petr Pavlu
2025-10-21  2:05   ` Aaron Tomlin
2025-11-03  8:54   ` Hans Verkuil
2025-11-03  8:58     ` Daniel Gomez
2025-11-03  9:05       ` Hans Verkuil
2025-12-19 12:29   ` Matthieu Baerts
2025-12-19 12:41     ` Daniel Gomez
2025-12-19 12:44     ` Dan Carpenter [this message]
2025-12-19 14:59       ` Matthieu Baerts
2026-01-16 23:35         ` Chris Li
     [not found] ` <68ed624c.050a0220.3ba739.64ea@mx.google.com>
2025-10-14  5:41   ` [v2,0/3] " Kees Cook
2025-10-14  6:24     ` Ricardo Ribalda
2025-10-14 20:45       ` Kees Cook
2025-10-15  7:33         ` Ricardo Ribalda
2025-10-20 18:29           ` Kees Cook
2025-10-20 18:35             ` Ricardo Ribalda
2025-10-20 18:51               ` Kees Cook
2025-10-20 18:55                 ` Ricardo Ribalda
2025-11-11 13:14                 ` Daniel Gomez
2025-11-03 19:49 ` [PATCH v2 0/3] " Daniel Gomez
2025-11-04  0:13   ` Kees Cook
2025-11-04  6:35     ` Daniel Gomez
2025-11-04 10:35       ` Hans Verkuil
2025-11-04 12:03         ` Daniel Gomez
2025-11-04 20:35           ` Daniel Gomez
2025-11-04 20:59             ` Hans Verkuil
2025-11-05 13:03 ` Daniel Gomez
2025-11-05 13:06   ` Daniel Gomez
2025-11-11 11:42   ` Andy Shevchenko
2025-11-11 12:34     ` Daniel Gomez
2025-11-11 17:52     ` Uwe Kleine-König
2025-11-05 13:19 ` Daniel Gomez

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=aUVIlvOSvobrdrKV@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=da.gomez@kernel.org \
    --cc=hverkuil+cisco@kernel.org \
    --cc=hverkuil@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=rusty@rustcorp.com.au \
    --cc=samitolvanen@google.com \
    --cc=sparse@chrisli.org \
    --cc=tvboxspy@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.