2014-11-27 08:47:51 |
Stefan Bader |
bug |
|
|
added bug |
2014-11-27 08:48:03 |
Stefan Bader |
nominated for series |
|
Ubuntu Utopic |
|
2014-11-27 08:48:03 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Utopic) |
|
2014-11-27 08:49:22 |
Stefan Bader |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763831 |
|
2014-11-27 09:00:10 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
2014-11-27 09:00:11 |
Brad Figg |
linux (Ubuntu Utopic): status |
New |
Incomplete |
|
2014-11-27 09:43:20 |
Stefan Bader |
linux (Ubuntu): status |
Incomplete |
Triaged |
|
2014-11-27 09:43:24 |
Stefan Bader |
linux (Ubuntu Utopic): status |
Incomplete |
Triaged |
|
2014-11-27 09:51:43 |
Andy Whitcroft |
tags |
|
kernel-bug-break-fix |
|
2014-11-27 09:55:48 |
Stefan Bader |
description |
SRU Justification:
Impact: Since v3.15 the link of /proc/<pid>/exe will unconditionally be renamed to the previous name of a binary when the filename is short and the binary was running. For example foo is a daemon and running while dpkg installs a new version. dpkg will unpack as foo.dpkg-new first and then rename to foo. After that /proc/<pid>/exe of the running foo daemon will point to the (no non-existent) foo.dpkg-new. Which in turn causes start-stop-daemon if that is used post-install to fail finding the running instance.
Fix: Backport of the following upstream change (which came with v3.17):
From d2fa4a8476b911782f7e5167db18770222ac40c3 Mon Sep 17 00:00:00 2001
From: Mikhail Efremov <sem@altlinux.org>
Date: Wed, 24 Sep 2014 22:14:33 +0400
Subject: [PATCH] vfs: Don't exchange "short" filenames unconditionally.
Only exchange source and destination filenames
if flags contain RENAME_EXCHANGE.
In case if executable file was running and replaced by
other file /proc/PID/exe should still show correct file name,
not the old name of the file by which it was replaced.
Testcase: Any binary running that has a short (<= DNAME_INLINE_LEN) filename), copy the current binary to <oldname>.new and then move <oldname>.new to <oldname>. Now /proc/<pid>/exe of the running process points to <oldname>.new wihtout the change but remains to be <oldname> with the patch.
break-fix: da1ce0670c14d8380e423a3239e562a1dc15fa9e d2fa4a8476b911782f7e5167db18770222ac40c3 |
SRU Justification:
Impact: Since v3.15 the link of /proc/<pid>/exe will unconditionally be renamed to the previous name of a binary when the filename is short and the binary was running. For example foo is a daemon and running while dpkg installs a new version. dpkg will unpack as foo.dpkg-new first and then rename to foo. After that /proc/<pid>/exe of the running foo daemon will point to the (no non-existent) foo.dpkg-new. Which in turn causes start-stop-daemon if that is used post-install to fail finding the running instance.
Fix: Backport of the following upstream change (which came with v3.17):
From d2fa4a8476b911782f7e5167db18770222ac40c3 Mon Sep 17 00:00:00 2001
From: Mikhail Efremov <sem@altlinux.org>
Date: Wed, 24 Sep 2014 22:14:33 +0400
Subject: [PATCH] vfs: Don't exchange "short" filenames unconditionally.
Only exchange source and destination filenames
if flags contain RENAME_EXCHANGE.
In case if executable file was running and replaced by
other file /proc/PID/exe should still show correct file name,
not the old name of the file by which it was replaced.
Testcase: Any binary running that has a short (<= DNAME_INLINE_LEN) filename), copy the current binary to <oldname>.new and then move <oldname>.new to <oldname>. Now /proc/<pid>/exe of the running process points to <oldname>.new wihtout the change but remains to be <oldname> with the patch.
break-fix: da1ce0670c14d8380e423a3239e562a1dc15fa9e d2fa4a8476b911782f7e5167db18770222ac40c3
break-fix: da1ce0670c14d8380e423a3239e562a1dc15fa9e 3b01fb24b2a8cdfb49511046ad7d6463bdf0ed00 |
|
2014-11-27 10:16:51 |
Andy Whitcroft |
summary |
Uncondicionally exchanging short filenames breaks userspace |
Unconditionally exchanging short filenames breaks userspace /proc/$$/exe links |
|
2014-11-27 10:19:14 |
Stefan Bader |
description |
SRU Justification:
Impact: Since v3.15 the link of /proc/<pid>/exe will unconditionally be renamed to the previous name of a binary when the filename is short and the binary was running. For example foo is a daemon and running while dpkg installs a new version. dpkg will unpack as foo.dpkg-new first and then rename to foo. After that /proc/<pid>/exe of the running foo daemon will point to the (no non-existent) foo.dpkg-new. Which in turn causes start-stop-daemon if that is used post-install to fail finding the running instance.
Fix: Backport of the following upstream change (which came with v3.17):
From d2fa4a8476b911782f7e5167db18770222ac40c3 Mon Sep 17 00:00:00 2001
From: Mikhail Efremov <sem@altlinux.org>
Date: Wed, 24 Sep 2014 22:14:33 +0400
Subject: [PATCH] vfs: Don't exchange "short" filenames unconditionally.
Only exchange source and destination filenames
if flags contain RENAME_EXCHANGE.
In case if executable file was running and replaced by
other file /proc/PID/exe should still show correct file name,
not the old name of the file by which it was replaced.
Testcase: Any binary running that has a short (<= DNAME_INLINE_LEN) filename), copy the current binary to <oldname>.new and then move <oldname>.new to <oldname>. Now /proc/<pid>/exe of the running process points to <oldname>.new wihtout the change but remains to be <oldname> with the patch.
break-fix: da1ce0670c14d8380e423a3239e562a1dc15fa9e d2fa4a8476b911782f7e5167db18770222ac40c3
break-fix: da1ce0670c14d8380e423a3239e562a1dc15fa9e 3b01fb24b2a8cdfb49511046ad7d6463bdf0ed00 |
SRU Justification:
Impact: Since v3.15 the link of /proc/<pid>/exe will unconditionally be renamed to the previous name of a binary when the filename is short and the binary was running. For example foo is a daemon and running while dpkg installs a new version. dpkg will unpack as foo.dpkg-new first and then rename to foo. After that /proc/<pid>/exe of the running foo daemon will point to the (no non-existent) foo.dpkg-new. Which in turn causes start-stop-daemon if that is used post-install to fail finding the running instance.
Fix: Backport of the following upstream change (which came with v3.17):
From d2fa4a8476b911782f7e5167db18770222ac40c3 Mon Sep 17 00:00:00 2001
From: Mikhail Efremov <sem@altlinux.org>
Date: Wed, 24 Sep 2014 22:14:33 +0400
Subject: [PATCH] vfs: Don't exchange "short" filenames unconditionally.
Only exchange source and destination filenames
if flags contain RENAME_EXCHANGE.
In case if executable file was running and replaced by
other file /proc/PID/exe should still show correct file name,
not the old name of the file by which it was replaced.
Testcase: Any binary running that has a short (<= DNAME_INLINE_LEN) filename), copy the current binary to <oldname>.new and then move <oldname>.new to <oldname>. Now /proc/<pid>/exe of the running process points to <oldname>.new wihtout the change but remains to be <oldname> with the patch.
break-fix: da1ce0670c14d8380e423a3239e562a1dc15fa9e d2fa4a8476b911782f7e5167db18770222ac40c3
break-fix: da1ce0670c14d8380e423a3239e562a1dc15fa9e a28ddb87cdddb0db57466ba7f59f831002f4340c |
|
2014-11-27 10:28:34 |
Andy Whitcroft |
linux (Ubuntu Utopic): status |
Triaged |
Confirmed |
|
2014-11-27 10:28:39 |
Andy Whitcroft |
linux (Ubuntu): status |
Triaged |
Fix Committed |
|
2015-01-07 09:17:01 |
Andy Whitcroft |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
2015-01-12 09:51:15 |
Andy Whitcroft |
linux (Ubuntu Utopic): status |
Confirmed |
Fix Committed |
|
2015-02-01 08:42:03 |
Andy Whitcroft |
linux (Ubuntu Utopic): status |
Fix Committed |
Fix Released |
|
2015-02-01 08:42:09 |
Andy Whitcroft |
tags |
kernel-bug-break-fix |
|
|