[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANeycqptxu1qWAHLc76krDmfgesANPX+FLEV51qhtXam6Ky9nQ@mail.gmail.com>
Date: Tue, 3 Oct 2023 10:55:44 -0300
From: Wedson Almeida Filho <wedsonaf@...il.com>
To: Dominique Martinet <asmadeus@...ewreck.org>
Cc: Eric Van Hensbergen <ericvh@...nel.org>,
Christian Schoenebeck <linux_oss@...debyte.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Wedson Almeida Filho <walmeida@...rosoft.com>,
Latchesar Ionkov <lucho@...kov.net>, v9fs@...ts.linux.dev
Subject: Re: [PATCH 03/29] 9p: move xattr-related structs to .rodata
On Sat, 30 Sept 2023 at 06:03, Dominique Martinet
<asmadeus@...ewreck.org> wrote:
>
> Christian Schoenebeck wrote on Sat, Sep 30, 2023 at 10:12:25AM +0200:
> > On Saturday, September 30, 2023 7:00:07 AM CEST Wedson Almeida Filho wrote:
> > > From: Wedson Almeida Filho <walmeida@...rosoft.com>
> > >
> > > This makes it harder for accidental or malicious changes to
> > > v9fs_xattr_user_handler, v9fs_xattr_trusted_handler,
> > > v9fs_xattr_security_handler, or v9fs_xattr_handlers at runtime.
> > >
> > > Cc: Eric Van Hensbergen <ericvh@...nel.org>
> > > Cc: Latchesar Ionkov <lucho@...kov.net>
> > > Cc: Dominique Martinet <asmadeus@...ewreck.org>
> > > Cc: Christian Schoenebeck <linux_oss@...debyte.com>
> > > Cc: v9fs@...ts.linux.dev
> > > Signed-off-by: Wedson Almeida Filho <walmeida@...rosoft.com>
> >
> > Reviewed-by: Christian Schoenebeck <linux_oss@...debyte.com>
Thanks for the review, Christian!
> Looks good to me on principle as well (and it should blow up immediately
> on testing in the unlikely case there's a problem...)
>
> Eric, I don't think you have anything planned for this round?
> There's another data race patch laying around that we didn't submit for
> 6.6, shall I take these two for now?
>
> (Assuming this patch series is meant to be taken up by individual fs
> maintainers independantly, it's never really clear with such large
> swatches of patchs and we weren't in Cc of a cover letter if there was
> any... In the future it'd help if either there's a clear cover letter
> everyone is in Cc at (some would say keep everyone in cc of all
> patches!), or just send these in a loop so they don't appear to be part
> of a series and each maintainer deals with it as they see fit)
There is a cover letter
(https://lore.kernel.org/all/20230930050033.41174-1-wedsonaf@gmail.com/),
apologies for not CCing you there. I was trying to avoid spamming
maintainers with unrelated changes.
We need changes in fs/xattr.c (which are in the first patch of the
series) to avoid warnings, so unfortunately this can't be taken
individually. My thought was that individual fs maintainers would
review/ack the patches and this would be taken through the fs tree.
>
> --
> Dominique
Powered by blists - more mailing lists