From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
petrm@nvidia.com, willemb@google.com, sdf@fomichev.me,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: net: exit cleanly on SIGTERM / timeout
Date: Mon, 28 Apr 2025 13:24:25 -0700 [thread overview]
Message-ID: <20250428132425.318f2a51@kernel.org> (raw)
In-Reply-To: <680cf896280c4_193a06294a6@willemb.c.googlers.com.notmuch>
On Sat, 26 Apr 2025 11:15:34 -0400 Willem de Bruijn wrote:
> > @@ -193,6 +198,19 @@ KSFT_DISRUPTIVE = True
> > return env
> >
> >
> > +term_cnt = 0
> > +
>
> A bit ugly to initialize this here. Also, it already is initialized
> below.
We need a global so that the signal handler can access it.
Python doesn't have syntax to define a variable without a value.
Or do you suggest term_cnt = None ?
The whole term_cnt dance is super ugly, couldn't think of a cleaner way.
It's really annoying that ksft infra sends 2 terminating signals one
immediately after the other :|
> > +def _ksft_intr(signum, frame):
> > + # ksft runner.sh sends 2 SIGTERMs in a row on a timeout
> > + # if we don't ignore the second one it will stop us from handling cleanup
> > + global term_cnt
> > + term_cnt += 1
> > + if term_cnt == 1:
> > + raise KsftTerminate()
> > + else:
> > + ksft_pr(f"Ignoring SIGTERM (cnt: {term_cnt}), already exiting...")
> > +
> > +
> > def ksft_run(cases=None, globs=None, case_pfx=None, args=()):
> > cases = cases or []
> >
> > @@ -205,6 +223,10 @@ KSFT_DISRUPTIVE = True
> > cases.append(value)
> > break
> >
> > + global term_cnt
> > + term_cnt = 0
> > + prev_sigterm = signal.signal(signal.SIGTERM, _ksft_intr)
> > +
> > totals = {"pass": 0, "fail": 0, "skip": 0, "xfail": 0}
> >
> > print("TAP version 13")
> > @@ -229,11 +251,12 @@ KSFT_DISRUPTIVE = True
> > cnt_key = 'xfail'
> > except BaseException as e:
> > stop |= isinstance(e, KeyboardInterrupt)
> > + stop |= isinstance(e, KsftTerminate)
> > tb = traceback.format_exc()
> > for line in tb.strip().split('\n'):
> > ksft_pr("Exception|", line)
> > if stop:
> > - ksft_pr("Stopping tests due to KeyboardInterrupt.")
> > + ksft_pr(f"Stopping tests due to {type(e).__name__}.")
> > KSFT_RESULT = False
> > cnt_key = 'fail'
> >
> > @@ -248,6 +271,8 @@ KSFT_DISRUPTIVE = True
> > if stop:
> > break
> >
> > + signal.signal(signal.SIGTERM, prev_sigterm)
> > +
>
> Why is prev_sigterm saved and reassigned as handler here?
Because we ignore all signals when cnt > 2 I didn't want to keep our
handler installed. Just in case something after ksft_run() hangs.
It should be equivalent to
signal.signal(signal.SIGTERM, signal.SIG_DLF)
if the prev is of concern. Then again keeping prev doesn't change #LOC
next prev parent reply other threads:[~2025-04-28 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 15:17 [PATCH net-next] selftests: net: exit cleanly on SIGTERM / timeout Jakub Kicinski
2025-04-26 15:15 ` Willem de Bruijn
2025-04-28 20:24 ` Jakub Kicinski [this message]
2025-04-29 1:27 ` Willem de Bruijn
2025-04-29 14:49 ` Paolo Abeni
2025-04-29 17:07 ` Jakub Kicinski
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=20250428132425.318f2a51@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).