All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Changbin Du <changbin.du@huawei.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Changbin Du <changbin.du@huawei.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH v4] tools: jobserver: Prevent deadlock caused by incorrect jobserver configuration and enhance error reporting
Date: Mon, 12 Jan 2026 09:48:21 -0700	[thread overview]
Message-ID: <87344a22wa.fsf@trenco.lwn.net> (raw)
In-Reply-To: <87v7h6241p.fsf@trenco.lwn.net>

Jonathan Corbet <corbet@lwn.net> writes:

> Jonathan Corbet <corbet@lwn.net> writes:
>
>> The warning comes from JobserverExec::open(), for an exception that
>> appears to be expected.  This is the sort of use of exceptions that has
>> made me almost swear off them entirely in Python - it's a huge try block
>> that is using exceptions to hide a bunch of the assumptions and logic.
>> I'll be posting a patch shortly to remove this non-exceptional exception
>> case.
>
> Here's a first step, just to show what I have in mind.

So FYI I'm going to add this into docs-next just to avoid adding a
potentially worrisome build warning to linux-next.  It's not yet in
docs-mw, so it's easily removable if a better way comes along.

jon

  reply	other threads:[~2026-01-12 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 11:38 [PATCH v4] tools: jobserver: Prevent deadlock caused by incorrect jobserver configuration and enhance error reporting Changbin Du
2026-01-12 16:08 ` Jonathan Corbet
2026-01-12 16:23   ` Jonathan Corbet
2026-01-12 16:48     ` Jonathan Corbet [this message]
2026-01-12 16:52     ` Mauro Carvalho Chehab
2026-01-13  1:52   ` duchangbin

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=87344a22wa.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=changbin.du@huawei.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.