linux-kernel - core dumps and prctl(PR_SET

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CALqGcGppqq0bN80ueGbdicB9=GGzkO2xm-4oUJHb=-WqsS0Pdg@mail.gmail.com>
Date:	Thu, 17 Nov 2011 13:36:50 +0100
From:	Christoph Mathys <eraserix@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: core dumps and prctl(PR_SET_NAME)

Hello!

We've recently started naming our threads using prctl(PR_SET_NAME,
...). For core dumps, we use the pattern "%e.core". %e is supposed to
expand to (according to Documentation/sysctl/kernel.txt of 3.0.9):

%e	executable filename (may be shortened)

However, after prctl was called, %e will expand to whatever name was
set in the call, not the executable filename anymore. This is not what
I would expect when reading the documentation. It also strikes me as
somewhat impractical. How do I know which application dumped core if
it should happen to assign names to its threads?

We are currently on 3.0.9 with PREEMPT_RT 25.

Please CC me on replies. Thanks!
Christoph
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/