Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Mathias Krause <minipli@grsecurity.net>,
	Philipp Reisner <philipp.reisner@linbit.com>,
	Lars Ellenberg <lars.ellenberg@linbit.com>
Cc: drbd-dev@lists.linbit.com
Subject: Re: [PATCH] compat: make block_device_operations tests grsec compatible
Date: Tue, 18 Nov 2025 11:50:08 +0100	[thread overview]
Message-ID: <a7d484bf-4812-4367-8fca-575a56529c67@linbit.com> (raw)
In-Reply-To: <20251110125924.511384-1-minipli@grsecurity.net>

Am 10.11.25 um 13:59 schrieb Mathias Krause:
> The grsecurity patch enforces that instances of certain types are always
> constified, with the help of a compiler plugin. One of these types is
> 'struct block_device_operations'. Code that tries to modify a such-typed
> object will cause compiler errors, leading to wrong results for the
> kernel compatibility tests.
> 
> Change these tests to do direct type compare tests instead of trying to
> modify the object, making them compatible with grsecurity kernels.
> 
> Signed-off-by: Mathias Krause <minipli@grsecurity.net>

Thanks, applied: https://github.com/LINBIT/drbd/commit/376a2932bf8f44dd0a18bc70f3309f3e71e0d37d

-- 
Christoph Böhmwalder
LINBIT | Keeping the Digital World Running
DRBD HA —  Disaster Recovery — Software defined Storage


      reply	other threads:[~2025-11-18 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 12:59 [PATCH] compat: make block_device_operations tests grsec compatible Mathias Krause
2025-11-18 10:50 ` Christoph Böhmwalder [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=a7d484bf-4812-4367-8fca-575a56529c67@linbit.com \
    --to=christoph.boehmwalder@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=minipli@grsecurity.net \
    --cc=philipp.reisner@linbit.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