From: Andrew Donnellan <ajd@linux.ibm.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Frederic Barrat" <fbarrat@linux.ibm.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/9] ocxl: Constify 'struct bin_attribute'
Date: Wed, 18 Dec 2024 18:21:45 +1100 [thread overview]
Message-ID: <3e67ac908ed4ea41290b8eb42d4fbdbe5a093b08.camel@linux.ibm.com> (raw)
In-Reply-To: <20241216-sysfs-const-bin_attr-misc-drivers-v1-1-d50ff7b21367@weissschuh.net>
On Mon, 2024-12-16 at 12:32 +0100, Thomas Weißschuh wrote:
> The sysfs core now allows instances of 'struct bin_attribute' to be
> moved into read-only memory. Make use of that to protect them against
> accidental or malicious modifications.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Acked-by: Andrew Donnellan <ajd@linux.ibm.com>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2024-12-18 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 11:32 [PATCH 0/9] misc: constify " Thomas Weißschuh
2024-12-16 11:32 ` [PATCH 1/9] ocxl: Constify " Thomas Weißschuh
2024-12-18 7:21 ` Andrew Donnellan [this message]
2024-12-16 11:32 ` [PATCH 2/9] cxl: " Thomas Weißschuh
2024-12-18 7:21 ` Andrew Donnellan
2024-12-16 11:32 ` [PATCH 3/9] misc: sram: constify " Thomas Weißschuh
2024-12-16 11:32 ` [PATCH 4/9] misc: c2port: Calculate bin_attribute size through group callback Thomas Weißschuh
2024-12-16 11:33 ` [PATCH 5/9] misc: c2port: Constify 'struct bin_attribute' Thomas Weißschuh
2024-12-16 11:33 ` [PATCH 6/9] misc: pch_phub: " Thomas Weißschuh
2024-12-16 11:33 ` [PATCH 7/9] misc: eeprom/idt_89hpesx: " Thomas Weißschuh
2024-12-16 11:33 ` [PATCH 8/9] misc: eeprom/max6875: " Thomas Weißschuh
2024-12-16 11:33 ` [PATCH 9/9] misc: ds1682: " Thomas Weißschuh
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=3e67ac908ed4ea41290b8eb42d4fbdbe5a093b08.camel@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=linuxppc-dev@lists.ozlabs.org \
/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®