public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@oracle.com>
To: Kees Cook <kees@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Allen Pais <apais@linux.microsoft.com>,
	Brian Mak <makb@juniper.net>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Jeff Xu <jeffxu@chromium.org>,
	Roman Kisel <romank@linux.microsoft.com>,
	regressions@lists.linux.dev
Subject: Re: [GIT PULL] execve updates for v6.12-rc1
Date: Thu, 26 Sep 2024 20:29:01 +0200	[thread overview]
Message-ID: <d122ece6-3606-49de-ae4d-8da88846bef2@oracle.com> (raw)
In-Reply-To: <202409160138.7E27F1A55@keescook>


On 16/09/2024 10:39, Kees Cook wrote:
> Hi Linus,
> 
> Please pull these execve updates for v6.12-rc1. Note there is a trivial
> merge conflict between this and mm, which was resolved in -next with:
> https://lore.kernel.org/linux-next/20240909171843.78c294da@canb.auug.org.au/
> 
> Thanks!
> 
> -Kees
> 
> The following changes since commit de9c2c66ad8e787abec7c9d7eff4f8c3cdd28aed:
> 
>    Linux 6.11-rc2 (2024-08-04 13:50:53 -0700)
> 
> are available in the Git repository at:
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/execve-v6.12-rc1
> 
> for you to fetch changes up to 44f65d900698278a8451988abe0d5ca37fd46882:
> 
>    binfmt_elf: mseal address zero (2024-08-14 09:56:48 -0700)
> 
> ----------------------------------------------------------------
> execve updates for v6.12-rc1
> 
> - binfmt_elf: Dump smaller VMAs first in ELF cores (Brian Mak)
> 
> - binfmt_elf: mseal address zero (Jeff Xu)
> 
> - binfmt_elf, coredump: Log the reason of the failed core dumps
>    (Roman Kisel)

Hi,

This last commit seems to introduce a regression for me, creating a
completely unkillable process (but idle/0% CPU) that is stuck here:

$ sudo cat /proc/2453/stack
[<0>] do_exit+0xee/0xac0
[<0>] do_group_exit+0x34/0x90
[<0>] get_signal+0xa63/0xa70
[<0>] arch_do_signal_or_restart+0x42/0x260
[<0>] irqentry_exit_to_user_mode+0x1e0/0x250
[<0>] irqentry_exit+0x43/0x50
[<0>] exc_page_fault+0x94/0x1d0
[<0>] asm_exc_page_fault+0x27/0x30

$ cat /proc/2453/status
...
State:  I (idle)
...
TracerPid:      0
...
Kthread:        0
VmPeak:     2240 kB
VmSize:     2240 kB
VmLck:         0 kB
VmPin:         0 kB
VmHWM:       568 kB
VmRSS:       568 kB
RssAnon:             136 kB
RssFile:             432 kB
RssShmem:              0 kB
VmData:      420 kB
VmStk:       132 kB
VmExe:      1644 kB
VmLib:        16 kB
VmPTE:        60 kB
VmSwap:        0 kB
HugetlbPages:          0 kB
CoreDumping:    1
THP_enabled:    1
untag_mask:     0xffffffffffffffff
Threads:        1
SigQ:   0/62622
SigPnd: 0000000000000100
ShdPnd: 0000000000000100
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 00000000000020db
...

The process is so unkillable I can't even shut my laptop down without
holding the power button for 5 seconds -- apart from that, everything
works correctly.

Bisection ended up here:

# first bad commit: [fb97d2eb542faf19a8725afbd75cbc2518903210] 
binfmt_elf, coredump: Log the reason of the failed core dumps

I have to admit I don't immediately see what's wrong with the patch.


Vegard

  parent reply	other threads:[~2024-09-26 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  8:39 [GIT PULL] execve updates for v6.12-rc1 Kees Cook
2024-09-18 10:40 ` pr-tracker-bot
2024-09-26 18:29 ` Vegard Nossum [this message]
2024-09-26 18:43   ` Linus Torvalds
2024-09-26 19:09     ` Eric W. Biederman
2024-09-26 19:17       ` Linus Torvalds
2024-09-26 20:37         ` Eric W. Biederman
2024-09-28 21:09   ` Kees Cook

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=d122ece6-3606-49de-ae4d-8da88846bef2@oracle.com \
    --to=vegard.nossum@oracle.com \
    --cc=apais@linux.microsoft.com \
    --cc=ebiederm@xmission.com \
    --cc=jeffxu@chromium.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=makb@juniper.net \
    --cc=regressions@lists.linux.dev \
    --cc=romank@linux.microsoft.com \
    --cc=torvalds@linux-foundation.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