netdev - Re: [PATCH net] selftests: netfilter: tone-down conntrack clash test

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250721075630.73f77af9@kernel.org>
Date: Mon, 21 Jul 2025 07:56:30 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Florian Westphal <fw@...len.de>
Cc: netdev@...r.kernel.org, pablo@...filter.org, pabeni@...hat.com
Subject: Re: [PATCH net] selftests: netfilter: tone-down conntrack clash
 test

On Sat, 19 Jul 2025 09:06:31 +0200 Florian Westphal wrote:
> Jakub Kicinski <kuba@...nel.org> wrote:
> > Hm, someone set this patch to Deferred and Archived in patchwork,  
> 
> I did. 

Please use pw-bot commands in the future, this way everyone knows
what's going on.

Quoting documentation:

  Updating patch status
  ~~~~~~~~~~~~~~~~~~~~~

  Contributors and reviewers do not have the permissions to update patch
  state directly in patchwork. Patchwork doesn't expose much information
  about the history of the state of patches, therefore having multiple
  people update the state leads to confusion.

  Instead of delegating patchwork permissions netdev uses a simple mail
  bot which looks for special commands/lines within the emails sent to
  the mailing list. For example to mark a series as Changes Requested
  one needs to send the following line anywhere in the email thread::

    pw-bot: changes-requested

  As a result the bot will set the entire series to Changes Requested.
  This may be useful when author discovers a bug in their own series
  and wants to prevent it from getting applied.

  The use of the bot is entirely optional, if in doubt ignore its existence
  completely. Maintainers will classify and update the state of the patches
  themselves. No email should ever be sent to the list with the main purpose
  of communicating with the bot, the bot commands should be seen as metadata.

  The use of the bot is restricted to authors of the patches (the ``From:``
  header on patch submission and command must match!), maintainers of
  the modified code according to the MAINTAINERS file (again, ``From:``
  must match the MAINTAINERS entry) and a handful of senior reviewers.

  Bot records its activity here:

    https://netdev.bots.linux.dev/pw-bot.html

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#updating-patch-status