mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: duchangbin <changbin.du@huawei.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: duchangbin <changbin.du@huawei.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	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: Tue, 13 Jan 2026 01:52:34 +0000	[thread overview]
Message-ID: <34c98e3ca24e4c88b9ba61c6f637671b@huawei.com> (raw)
In-Reply-To: <874ioq3jad.fsf@trenco.lwn.net>

On Mon, Jan 12, 2026 at 09:08:58AM -0700, Jonathan Corbet wrote:
> Changbin Du <changbin.du@huawei.com> writes:
> 
> > When using GNU Make's jobserver feature in kernel builds, a bug in MAKEFLAGS
> > propagation caused "--jobserver-auth=r,w" to reference an unintended file
> > descriptor. This led to infinite loops in jobserver-exec's os.read() calls
> > due to empty token.
> >
> > My shell opened /etc/passwd for some reason without closing it, and as a
> > result, all child processes inherited this fd 3.
> >
> > $ ls -l /proc/self/fd
> > total 0
> > lrwx------ 1 changbin changbin 64 Dec 25 13:03 0 -> /dev/pts/1
> > lrwx------ 1 changbin changbin 64 Dec 25 13:03 1 -> /dev/pts/1
> > lrwx------ 1 changbin changbin 64 Dec 25 13:03 2 -> /dev/pts/1
> > lr-x------ 1 changbin changbin 64 Dec 25 13:03 3 -> /etc/passwd
> > lr-x------ 1 changbin changbin 64 Dec 25 13:03 4 -> /proc/1421383/fd
> >
> > In this case, the `make` should open a new file descriptor for jobserver
> > control, but clearly, it did not do so and instead still passed fd 3 as
> > "--jobserver-auth=3,4" in MAKEFLAGS. (The version of my gnu make is 4.3)
> >
> > This update ensures robustness against invalid jobserver configurations,
> > even when `make` incorrectly pass non-pipe file descriptors.
> >  * Rejecting empty reads to prevent infinite loops on EOF.
> >  * Clearing `self.jobs` to avoid writing to incorrect files if invalid tokens
> >    are detected.
> >  * Printing detailed error messages to stderr to inform the user.
> >
> > Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > Signed-off-by: Changbin Du <changbin.du@huawei.com>
> 
> So I've applied this; it appears to work, though I can't really test the
> error case that it is intended to fix.
> 

Here's my local test result in case you need it.

$ make ARCH=riscv LLVM=1 LLVM_IAS=1 -j$(nproc) Image
  ...
  AR      drivers/built-in.a
  AR      built-in.a
  AR      vmlinux.a
  GEN     .tmp_initcalls.lds
jobserver: warning: ValueError("unexpected empty token from jobserver fd, invalid '--jobserver-auth=' setting?")
  LD      vmlinux.o

-- 
Cheers,
Changbin Du

      parent reply	other threads:[~2026-01-13  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 11:38 Changbin Du
2026-01-12 16:08 ` Jonathan Corbet
2026-01-12 16:23   ` Jonathan Corbet
2026-01-12 16:48     ` Jonathan Corbet
2026-01-12 16:52     ` Mauro Carvalho Chehab
2026-01-13  1:52   ` duchangbin [this message]

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=34c98e3ca24e4c88b9ba61c6f637671b@huawei.com \
    --to=changbin.du@huawei.com \
    --cc=corbet@lwn.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®