public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Adam Radford <aradford@gmail.com>,
	Bradley Grove <linuxdrivers@attotech.com>,
	Tyrel Datwyler <tyreld@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Naveen N Rao <naveen@kernel.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	James Smart <james.smart@broadcom.com>,
	Dick Kennedy <dick.kennedy@broadcom.com>,
	Brian King <brking@us.ibm.com>,
	Saurav Kashyap <skashyap@marvell.com>,
	Javed Hasan <jhasan@marvell.com>,
	GR-QLogic-Storage-Upstream@marvell.com,
	Nilesh Javali <njavali@marvell.com>,
	Manish Rangankar <mrangankar@marvell.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/11] scsi: Constify 'struct bin_attribute'
Date: Thu, 02 Jan 2025 15:10:33 -0500	[thread overview]
Message-ID: <yq134i1f03y.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20241216-sysfs-const-bin_attr-scsi-v1-0-f0a5e54b3437@weissschuh.net> ("Thomas Weißschuh"'s message of "Mon, 16 Dec 2024 12:29:07 +0100")


Thomas,

> 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.

Applied to 6.14/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2025-01-02 20:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 11:29 [PATCH 00/11] scsi: Constify 'struct bin_attribute' Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 01/11] scsi: core: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 02/11] scsi: 3w-sas: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 03/11] scsi: arcmsr: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 04/11] scsi: esas2r: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 05/11] scsi: ibmvfc: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 06/11] scsi: lpfc: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 07/11] scsi: ipr: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 08/11] scsi: qedf: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 09/11] scsi: qedi: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 10/11] scsi: qla2xxx: " Thomas Weißschuh
2024-12-16 11:29 ` [PATCH 11/11] scsi: qla4xxx: " Thomas Weißschuh
2025-01-02 20:10 ` Martin K. Petersen [this message]
2025-01-10 21:16 ` [PATCH 00/11] scsi: " Martin K. Petersen

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=yq134i1f03y.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=aradford@gmail.com \
    --cc=brking@us.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dick.kennedy@broadcom.com \
    --cc=james.smart@broadcom.com \
    --cc=jhasan@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=linuxdrivers@attotech.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=mrangankar@marvell.com \
    --cc=naveen@kernel.org \
    --cc=njavali@marvell.com \
    --cc=npiggin@gmail.com \
    --cc=skashyap@marvell.com \
    --cc=tyreld@linux.ibm.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