linux-kernel - Re: /proc/<pid>/exe symlink behavior change in >=3.15.

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 7 Sep 2014 01:02:58 +0200
From:	Richard Weinberger <richard.weinberger@...il.com>
To:	Piotr Karbowski <piotr.karbowski@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: /proc/<pid>/exe symlink behavior change in >=3.15.

On Sat, Sep 6, 2014 at 11:44 PM, Piotr Karbowski
<piotr.karbowski@...il.com> wrote:
> Hi,
>
> Starting with kernel 3.15 the 'exe' symlink under /proc/<pid>/ acts diffrent
> than it used to in all the pre-3.15 kernels.
>
> The usecase:
>
> run /root/testbin (app that just sleeps)
> cp /root/testbin /root/testbin.new
> mv /root/testbin.new /root/testbin
> ls -al /proc/`pidof testbin`/exe
>
> <=3.14: /root/testbin (deleted)
>>=3.15: /root/testbin.new (deleted)
>
> Was the change intentional? It does render my system unusable and I failed
> to find a information about such change in the ChangeLog.

Can you please find the offending commit?
Using an automated bisect run this should be easily doable.

-- 
Thanks,
//richard
--
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/