linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: =?utf-8?q?Willy_Tarreau_=3Cw=401wt=2Eeu=3E=2C_Thomas_Wei=C3=9Fschuh_=3Cl?=@vger.kernel.org,
	=?utf-8?q?inux=40weissschuh=2Enet=3E?=@vger.kernel.org
Cc: Christian Brauner <brauner@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, Zhangjin Wu <falcon@tinylab.org>,
	Arnd Bergmann <arnd@arndb.de>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 0/2] proc: proc_setattr for /proc/$PID/net
Date: Thu, 13 Jul 2023 13:58:48 +0200	[thread overview]
Message-ID: <20230713-schwalben-anproben-6af2eac149fd@brauner> (raw)
In-Reply-To: <20230624-proc-net-setattr-v1-0-73176812adee@weissschuh.net>

On Sat, 24 Jun 2023 12:30:45 +0200, Thomas Weißschuh wrote:
> /proc/$PID/net currently allows the setting of file attributes,
> in contrast to other /proc/$PID/ files and directories.
> 
> This would break the nolibc testsuite so the first patch in the series
> removes the offending testcase.
> The "fix" for nolibc-test is intentionally kept trivial as the series
> will most likely go through the filesystem tree and if conflicts arise,
> it is obvious on how to resolve them.
> 
> [...]

I've picked both for now. Let me know if I should do something else.
In any case, this needs long soaking in -next.

---

Applied to the fs.proc.net.uapi branch of the vfs/vfs.git tree.
Patches in the fs.proc.net.uapi branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: fs.proc.net.uapi

[1/2] selftests/nolibc: drop test chmod_net
      https://git.kernel.org/vfs/vfs/c/49319832de90
[2/2] proc: use generic setattr() for /proc/$PID/net
      https://git.kernel.org/vfs/vfs/c/18e66ae67673

      parent reply	other threads:[~2023-07-13 12:00 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
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 [this message]

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=20230713-schwalben-anproben-6af2eac149fd@brauner \
    --to=brauner@kernel.org \
    --cc==?utf-8?q?Willy_Tarreau_=3Cw=401wt=2Eeu=3E=2C_Thomas_Wei=C3=9Fschuh_=3Cl?=@vger.kernel.org \
    --cc==?utf-8?q?inux=40weissschuh=2Enet=3E?=@vger.kernel.org \
    --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 \
    /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;
as well as URLs for NNTP newsgroup(s).