[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re: Re: Re: [PATCH v2] treewide: const qualify ctl_tables where applicable
- To: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- From: Joel Granados <joel.granados@xxxxxxxxxx>
- Date: Tue, 28 Jan 2025 12:22:37 +0100
- Cc: Jani Nikula <jani.nikula@xxxxxxxxx>, Ard Biesheuvel <ardb@xxxxxxxxxx>, Alexander Gordeev <agordeev@xxxxxxxxxxxxx>, Thomas Weißschuh <linux@xxxxxxxxxxxxxx>, Kees Cook <kees@xxxxxxxxxx>, Luis Chamberlain <mcgrof@xxxxxxxxxx>, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linuxppc-dev@xxxxxxxxxxxxxxxx, linux-riscv@xxxxxxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, linux-crypto@xxxxxxxxxxxxxxx, openipmi-developer@xxxxxxxxxxxxxxxxxxxxx, intel-gfx@xxxxxxxxxxxxxxxxxxxxx, dri-devel@xxxxxxxxxxxxxxxxxxxxx, intel-xe@xxxxxxxxxxxxxxxxxxxxx, linux-hyperv@xxxxxxxxxxxxxxx, linux-rdma@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx, linux-serial@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-aio@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, netfs@xxxxxxxxxxxxxxx, codalist@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, ocfs2-devel@xxxxxxxxxxxxxxx, fsverity@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, io-uring@xxxxxxxxxxxxxxx, bpf@xxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx, linux-trace-kernel@xxxxxxxxxxxxxxx, linux-hardening@xxxxxxxxxxxxxxx, apparmor@xxxxxxxxxxxxxxxx, linux-security-module@xxxxxxxxxxxxxxx, keyrings@xxxxxxxxxxxxxxx, Song Liu <song@xxxxxxxxxx>, "Steven Rostedt (Google)" <rostedt@xxxxxxxxxxx>, "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, "Darrick J. Wong" <djwong@xxxxxxxxxx>, Corey Minyard <cminyard@xxxxxxxxxx>
- Delivery-date: Tue, 28 Jan 2025 11:23:01 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Mon, Jan 27, 2025 at 03:42:39PM +0000, Matthew Wilcox wrote:
> On Mon, Jan 27, 2025 at 04:55:58PM +0200, Jani Nikula wrote:
> > You could have static const within functions too. You get the rodata
> > protection and function local scope, best of both worlds?
>
> timer_active is on the stack, so it can't be static const.
>
> Does this really need to be cc'd to such a wide distribution list?
That is a very good question. I removed 160 people from the original
e-mail and left the ones that where previously involved with this patch
and left all the lists for good measure. But it seems I can reduce it
even more.
How about this: For these treewide efforts I just leave the people that
are/were involved in the series and add two lists: linux-kernel and
linux-hardening.
Unless someone screams, I'll try this out on my next treewide.
Thx for the feedback
Best
--
Joel Granados
|
