From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: linux@weissschuh.net, 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: Sun, 9 Jul 2023 11:29:47 +0200 [thread overview]
Message-ID: <20230709092947.GF9321@1wt.eu> (raw)
In-Reply-To: <20230630140609.263790-1-falcon@tinylab.org>
Hi,
On Fri, Jun 30, 2023 at 10:06:09PM +0800, Zhangjin Wu wrote:
> Hi, Thomas
>
> Just applied your patchset on v6.4, and then:
>
> - revert the 1st patch: 'selftests/nolibc: drop test chmod_net' manually
>
> - do the 'run' test of nolibc on arm/vexpress-a9
>
> The 'chmod_net' test of tools/testing/selftests/nolibc/nolibc-test.c
> really failed as expected (and therefore, should be removed):
>
> 11 chdir_root = 0 [OK]
> 12 chdir_dot = 0 [OK]
> 13 chdir_blah = -1 ENOENT [OK]
> 14 chmod_net = -1 EPERM [FAIL]
> 15 chmod_self = -1 EPERM [OK]
> 16 chmod_tmpdir = 0 [OK]
> 17 chown_self = -1 EPERM [OK]
>
> So, If this test result is enough for this patch, here is my:
>
> Tested-by: Zhangjin Wu <falcon@tinylab.org>
Now queued, thanks!
Willy
next prev parent reply other threads:[~2023-07-09 9:30 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 [this message]
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
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=20230709092947.GF9321@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=linux@weissschuh.net \
--cc=shuah@kernel.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