From: Joel Becker <jlbec@evilplan.org>
To: Breno Leitao <leitao@debian.org>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
Eric Dumazet <edumazet@google.com>,
Jonathan Corbet <corbet@lwn.net>,
hch@lst.de, netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH net-next v4 4/4] Documentation: netconsole: add support for cmdline targets
Date: Sat, 14 Oct 2023 17:55:30 -0700 [thread overview]
Message-ID: <ZSs4gvm8fx+BpfcQ@google.com> (raw)
In-Reply-To: <20231012111401.333798-5-leitao@debian.org>
On Thu, Oct 12, 2023 at 04:14:01AM -0700, Breno Leitao wrote:
> With the previous patches, there is no more limitation at modifying the
> targets created at boot time (or module load time).
>
> Document the way on how to create the configfs directories to be able to
> modify these netconsole targets.
>
> The design discussion about this topic could be found at:
> https://lore.kernel.org/all/ZRWRal5bW93px4km@gmail.com/
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Joel Becker <jlbec@evilplan.org>
> ---
> Documentation/networking/netconsole.rst | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/networking/netconsole.rst b/Documentation/networking/netconsole.rst
> index 7a9de0568e84..390730a74332 100644
> --- a/Documentation/networking/netconsole.rst
> +++ b/Documentation/networking/netconsole.rst
> @@ -99,9 +99,6 @@ Dynamic reconfiguration:
> Dynamic reconfigurability is a useful addition to netconsole that enables
> remote logging targets to be dynamically added, removed, or have their
> parameters reconfigured at runtime from a configfs-based userspace interface.
> -[ Note that the parameters of netconsole targets that were specified/created
> -from the boot/module option are not exposed via this interface, and hence
> -cannot be modified dynamically. ]
>
> To include this feature, select CONFIG_NETCONSOLE_DYNAMIC when building the
> netconsole module (or kernel, if netconsole is built-in).
> @@ -155,6 +152,25 @@ You can also update the local interface dynamically. This is especially
> useful if you want to use interfaces that have newly come up (and may not
> have existed when netconsole was loaded / initialized).
>
> +Netconsole targets defined at boot time (or module load time) with the
> +`netconsole=` param are assigned the name `cmdline<index>`. For example, the
> +first target in the parameter is named `cmdline0`. You can control and modify
> +these targets by creating configfs directories with the matching name.
> +
> +Let's suppose you have two netconsole targets defined at boot time::
> +
> + netconsole=4444@10.0.0.1/eth1,9353@10.0.0.2/12:34:56:78:9a:bc;4444@10.0.0.1/eth1,9353@10.0.0.3/12:34:56:78:9a:bc
> +
> +You can modify these targets in runtime by creating the following targets::
> +
> + mkdir cmdline0
> + cat cmdline0/remote_ip
> + 10.0.0.2
> +
> + mkdir cmdline1
> + cat cmdline1/remote_ip
> + 10.0.0.3
> +
> Extended console:
> =================
>
> --
> 2.34.1
>
--
f/8 and be there.
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2023-10-15 0:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 11:13 [PATCH net-next v4 0/4] net: netconsole: configfs entries for boot target Breno Leitao
2023-10-12 11:13 ` [PATCH net-next v4 1/4] netconsole: move init/cleanup functions lower Breno Leitao
2023-10-15 0:54 ` Joel Becker
2023-10-12 11:13 ` [PATCH net-next v4 2/4] netconsole: Initialize configfs_item for default targets Breno Leitao
2023-10-15 0:53 ` Joel Becker
2023-10-12 11:14 ` [PATCH net-next v4 3/4] netconsole: Attach cmdline target to dynamic target Breno Leitao
2023-10-15 0:55 ` Joel Becker
2023-10-12 11:14 ` [PATCH net-next v4 4/4] Documentation: netconsole: add support for cmdline targets Breno Leitao
2023-10-15 0:55 ` Joel Becker [this message]
2023-10-14 0:30 ` [PATCH net-next v4 0/4] net: netconsole: configfs entries for boot target patchwork-bot+netdevbpf
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=ZSs4gvm8fx+BpfcQ@google.com \
--to=jlbec@evilplan.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hch@lst.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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