From: Piotr Karbowski <piotr.karbowski@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: /proc/<pid>/exe symlink behavior change in >=3.15.
Date: Sun, 07 Sep 2014 12:20:16 +0200 [thread overview]
Message-ID: <540C3160.9040408@gmail.com> (raw)
In-Reply-To: <CAFLxGvx7-KR7JqeH3d5nZ6prSez-32BVq6-SNot3s+Nw=UBVhg@mail.gmail.com>
Hi,
On 09/07/2014 01:02 AM, Richard Weinberger wrote:
> Can you please find the offending commit?
> Using an automated bisect run this should be easily doable.
That would be it:
da1ce0670c14d8380e423a3239e562a1dc15fa9e is the first bad commit
commit da1ce0670c14d8380e423a3239e562a1dc15fa9e
Author: Miklos Szeredi <mszeredi@suse.cz>
Date: Tue Apr 1 17:08:43 2014 +0200
vfs: add cross-rename
If flags contain RENAME_EXCHANGE then exchange source and
destination files.
There's no restriction on the type of the files; e.g. a directory
can be
exchanged with a symlink.
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Reviewed-by: Jan Kara <jack@suse.cz>
Reviewed-by: J. Bruce Fields <bfields@redhat.com>
:040000 040000 86e9be1a42cb91c1068b76700c74ec7fdba5443c
e0269a1fffefe60cbd6d56ccab6485ff383d728d M fs
:040000 040000 e677e31ebb0a5b355cefe199cba9453800624905
7a083642c2ea0698d85bfc9e65b99e8cfb4a7440 M include
:040000 040000 266252c531debd56ae52e000ed1579dca19ddb35
bfcb75158276de3feafd45d726f3297dfc139389 M security
-- Piotr.
next prev parent reply other threads:[~2014-09-07 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 21:44 /proc/<pid>/exe symlink behavior change in >=3.15 Piotr Karbowski
2014-09-06 23:02 ` Richard Weinberger
2014-09-07 10:20 ` Piotr Karbowski [this message]
2014-09-07 7:56 ` Mateusz Guzik
2014-09-11 18:37 ` Piotr Karbowski
2014-09-11 23:39 ` Chuck Ebbert
2014-09-11 23:57 ` Mateusz Guzik
2014-09-15 14:14 ` Miklos Szeredi
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=540C3160.9040408@gmail.com \
--to=piotr.karbowski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/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.