nassh: sftp mount gets wedged: Files app thinks it's mounted, but Secure Shell doesn't |
||
Issue descriptionsteps to reproduce: - start sftp mount under CrOS - log out - log in - load Files app - mounts are still listed, but can't be used or unmounted the background page console has messages like: nassh.sftp.fsp.onUnmountRequested -> nassh.sftp.fsp.checkInstanceExists: SFTP Instance for file system id "dcf0" not found! and then we return w/out actually unmounting.
,
Apr 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/apps/libapps/+/7f3c7891fcf6c8d222d509132c124b0f0293a349 commit 7f3c7891fcf6c8d222d509132c124b0f0293a349 Author: Mike Frysinger <vapier@chromium.org> Date: Mon Apr 17 17:16:57 2017 nassh: sftp: allow unmounting of unknown (to us) mounts If a mount point gets wedged (for any reason), we should still allow users to break down the mount point. Otherwise they get stuck in a loop they can't recover from. In this case, if you create a mount, log out, then log back in, the Files app will remember the mount points, but Secure Shell won't. BUG= chromium:711722 Change-Id: Ib2060feaa6293752c84175fcac00e85ca68ae97d Reviewed-on: https://chromium-review.googlesource.com/478190 Reviewed-by: Brandon Gilmore <varz@google.com> Reviewed-by: Rob Ginda <rginda@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/7f3c7891fcf6c8d222d509132c124b0f0293a349/nassh/js/nassh_sftp_fsp.js
,
May 9 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by vapier@chromium.org
, Apr 17 2017