From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: Zhangjin Wu <falcon@tinylab.org>,
arnd@arndb.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org
Subject: Re: [PATCH 0/2] proc: proc_setattr for /proc/$PID/net
Date: Mon, 10 Jul 2023 09:09:20 +0200 [thread overview]
Message-ID: <ZKuuoB6fcAV3ucFM@1wt.eu> (raw)
In-Reply-To: <74eddce8-4f59-40c8-bc49-38c286a3cbb0@t-8ch.de>
On Sun, Jul 09, 2023 at 08:22:31PM +0200, Thomas Weißschuh wrote:
> On 2023-07-09 20:04:32+0200, Willy Tarreau wrote:
> > On Sun, Jul 09, 2023 at 07:57:27PM +0200, Thomas Weißschuh wrote:
> > > On 2023-07-09 19:27:53+0200, Willy Tarreau wrote:
> > > > On Sun, Jul 09, 2023 at 07:10:58PM +0200, Thomas Weißschuh wrote:
> > > > > On 2023-07-09 11:29:47+0200, Willy Tarreau wrote:
> > > > > > On Fri, Jun 30, 2023 at 10:06:09PM +0800, Zhangjin Wu wrote:
> > > > > >> [..]
> > > > > >
> > > > > > Now queued, thanks!
> > > > > > Willy
> > > > >
> > > > > Don't we need an Ack from the fs maintainers for the patch to
> > > > > fs/proc/proc_net.c ?
> > > > >
> > > > > Personally I expected this series to go in via the fs tree because of
> > > > > that patch.
> > > >
> > > > Gasp! You're totally right, I confused it with a test only changing
> > > > the nolibc-test file, as the chmod_net test appeared as a dependency!
> > > > Let me drop it from the series and push again.
> > >
> > > I think if this patch now also goes in via both the nolibc/rcu trees and
> > > the fs tree it would not be great.
> > >
> > > The best way forward would probably for you to rebase your tree on top
> > > of mainline after the fs tree has introduced both patches of the series
> > > into Linus' tree and then you can drop your copy of the test removal.
> >
> > Yeah I agree.
> >
> > > I want to keep both patches together because I expect the fs change to
> > > be backported and if it is backported on its own it will break
> > > nolibc-test in those trees.
> >
> > OK but we can also fix the test regardless, and mark it for backport, no ?
>
> That should work fine, too.
> Can you add the Fixes and Cc-stable tags in your tree and let the fs
> maintainers know?
OK here's what it's like now, let me know if you'd prefer any change:
commit 8c2e51e174ed0f998b6bd90244324a4966a55efc
Author: Thomas Weißschuh <linux@weissschuh.net>
Date: Sat Jun 24 12:30:46 2023 +0200
selftests/nolibc: drop test chmod_net
The test relies on /proc/$PID/net to allow chmod() operations.
It is the only file or directory in /proc/$PID/ to allow this and a bug.
That bug will be fixed in the next patch in the series and therefore
the test would start failing.
Link: https://lore.kernel.org/lkml/d0d111ef-edae-4760-83fb-36db84278da1@t-8ch.de/
Fixes: b4844fa0bdb4 ("selftests/nolibc: implement a few tests for various syscalls")
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Tested-by: Zhangjin Wu <falcon@tinylab.org>
Signed-off-by: Willy Tarreau <w@1wt.eu>
> Or do you want me to split and resend the series?
Not needed, thank you.
Willy
next prev parent reply other threads:[~2023-07-10 7:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 10:30 [PATCH 0/2] proc: proc_setattr for /proc/$PID/net Thomas Weißschuh
2023-06-24 10:30 ` [PATCH 1/2] selftests/nolibc: drop test chmod_net Thomas Weißschuh
2023-06-24 10:30 ` [PATCH 2/2] proc: use generic setattr() for /proc/$PID/net Thomas Weißschuh
2023-07-13 11:49 ` Christian Brauner
2023-06-30 14:06 ` [PATCH 0/2] proc: proc_setattr " Zhangjin Wu
2023-07-09 9:29 ` Willy Tarreau
2023-07-09 17:10 ` Thomas Weißschuh
2023-07-09 17:27 ` Willy Tarreau
2023-07-09 17:57 ` Thomas Weißschuh
2023-07-09 18:04 ` Willy Tarreau
2023-07-09 18:22 ` Thomas Weißschuh
2023-07-10 7:09 ` Willy Tarreau [this message]
2023-07-10 7:36 ` Thomas Weißschuh
2023-07-13 11:51 ` Christian Brauner
2023-07-13 12:04 ` Thomas Weißschuh
2023-07-13 11:58 ` Christian Brauner
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=ZKuuoB6fcAV3ucFM@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=thomas@t-8ch.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.