From: Andrew Lunn <andrew@lunn.ch>
To: Tobias Junghans <tobias.junghans@inhub.de>
Cc: Lee Jones <lee@kernel.org>,
linux-leds@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] leds: trigger: netdev: refactor netdev_event_requires_handling()
Date: Thu, 12 Jun 2025 14:26:11 +0200 [thread overview]
Message-ID: <556f0bb0-fd01-4e25-802e-7bbe98f0441f@lunn.ch> (raw)
In-Reply-To: <0bcb999e-f32c-499e-9a10-41334ffc2255@lunn.ch>
> Tomorrow i will look at the socket system calls and see how you get a
> processes network namespace.
current->nsproxy->net_ns gives the current processes network
namespace.
current is one of those historical odd things, like
jiffies. Originally it was a global variable, when the kernel
supported a single CPU, and hence only a single processes was ever
running. But with the change to SMP it became a #define for a function
call.
Andrew
next prev parent reply other threads:[~2025-06-12 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 11:40 [PATCH 0/2] leds: trigger: netdev: refactor event handling Tobias Junghans
2025-06-10 11:40 ` [PATCH 1/2] leds: trigger: netdev: separate event checks Tobias Junghans
2025-06-10 11:40 ` [PATCH 2/2] leds: trigger: netdev: refactor netdev_event_requires_handling() Tobias Junghans
2025-06-12 2:57 ` Andrew Lunn
2025-06-12 12:26 ` Andrew Lunn [this message]
2025-06-19 11:37 ` Lee Jones
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=556f0bb0-fd01-4e25-802e-7bbe98f0441f@lunn.ch \
--to=andrew@lunn.ch \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tobias.junghans@inhub.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox