"mountinfo" in chrome://system doesn't indicate if ecryptfs is used |
||||||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win7, OSX 10.9.5, etc...) What steps will reproduce the problem? (1) Log in as a user whose home dir is using eCryptfs (2) Open chrome://system What is the expected result? It displays lines with "ecryptfs" as the fs type. What happens instead? No "ecryptfs" included. Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Mar 21 2017
sorry about that, seems like `/proc/$(pgrep debugd)/mountinfo` doesn't contain the user mounts.
,
Mar 21 2017
I'll handle this.
,
Apr 10 2017
after Nth time of being bitten by this I put together https://chromium-review.googlesource.com/472311
,
Apr 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/710cb4b6b6ee2e9c750db6ce96255f211107704c commit 710cb4b6b6ee2e9c750db6ce96255f211107704c Author: Junichi Uekawa <uekawa@google.com> Date: Thu Apr 13 03:22:31 2017 debugd: Look at mountpoints from init instead of debugd. Debugd runs inside a mount namespace but not inside a pid namespace, so this gives a view of what is mounted. TEST=manually observe ext4 crypto system. BUG= chromium:703505 Change-Id: I1b53d37fcca1e6a887f6ed0137e58d6c797db1d2 Reviewed-on: https://chromium-review.googlesource.com/472311 Commit-Ready: Junichi Uekawa <uekawa@chromium.org> Tested-by: Junichi Uekawa <uekawa@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org> [modify] https://crrev.com/710cb4b6b6ee2e9c750db6ce96255f211107704c/debugd/src/log_tool.cc
,
Apr 13 2017
,
Apr 14 2017
I'd like to have this merged in M58 because we're trying to roll out this new file system in a subset of devices and knowing this in feedback reports is useful.
,
Apr 14 2017
(verified on caroline and kevin canary).
,
Apr 14 2017
This bug requires manual review: We are only 10 days from stable. Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 14 2017
,
Apr 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/8b72b83f89845d9c09600e18e61fe897602bc4d9 commit 8b72b83f89845d9c09600e18e61fe897602bc4d9 Author: Junichi Uekawa <uekawa@google.com> Date: Sat Apr 15 02:03:21 2017 debugd: Look at mountpoints from init instead of debugd. Debugd runs inside a mount namespace but not inside a pid namespace, so this gives a view of what is mounted. TEST=manually observe ext4 crypto system. BUG= chromium:703505 Change-Id: I1b53d37fcca1e6a887f6ed0137e58d6c797db1d2 Reviewed-on: https://chromium-review.googlesource.com/472311 Commit-Ready: Junichi Uekawa <uekawa@chromium.org> Tested-by: Junichi Uekawa <uekawa@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org> (cherry picked from commit 710cb4b6b6ee2e9c750db6ce96255f211107704c) Reviewed-on: https://chromium-review.googlesource.com/476371 Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Commit-Queue: Junichi Uekawa <uekawa@chromium.org> Trybot-Ready: Junichi Uekawa <uekawa@chromium.org> [modify] https://crrev.com/8b72b83f89845d9c09600e18e61fe897602bc4d9/debugd/src/log_tool.cc
,
Apr 17 2017
,
Apr 17 2017
to verify, chrome://system contains mountinfo with /home/.shadow/ ecryptfs mount points on ecryptfs systems and lots (63 for me) of mount points. It used to contain 26 mount points before.
,
Apr 18 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 19 2017
,
Apr 27 2017
Verified on build 9334.58.0 |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by hashimoto@chromium.org
, Mar 21 2017