unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43723@debbugs.gnu.org
Subject: bug#43723: 27.1; Errors in file-extended-attributes prevent from saving buffer
Date: Mon, 06 Jun 2022 19:53:34 +0300	[thread overview]
Message-ID: <8335gh91ip.fsf@gnu.org> (raw)
In-Reply-To: <87zgiprccq.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  06 Jun 2022 18:22:13 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 43723@debbugs.gnu.org
> Date: Mon, 06 Jun 2022 18:22:13 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > When some volume is mounted such that file-extended-attributes fails
> > for files there (because the agent used to mount doesn't support ACLs
> > or SELinux), this prevents users from saving their edits to files on
> > that volume, because file-extended-attributes signals an error.  This
> > appears as a regression to users because Emacs 26 silently ignored
> > such errors.
> >
> > To allow users to save the files in these cases, but still keep them
> > informed about the loss of potentially important attributes, Emacs
> > should probably warn about this, allow the user to decide he/she wants
> > to ignore the problem, and record this fact somewhere, to avoid asking
> > the same question again for the same volume.
> 
> Do you have a test case to reproduce this problem?  I don't really use
> SELinux myself...

No, I don't have a recipe.

This bug report was the result of this discussion on emacs-devel:

  https://lists.gnu.org/archive/html/emacs-devel/2020-09/msg02248.html

The basic concern is that Emacs 26 silently ignored errors in file-acl
and file-selinux-context, whereas Emacs 27 and later doesn't ignore
them.  My point was that preventing the user from saving the edits
just because we cannot preserve the ACLs is too radical, since most
users don't care about ACLs, and because support for ACLs on volumes
mounted by all kinds of network disk drivers that have trouble mapping
extended attributes between different systems.

You can easily simulate this situation by writing a replacement for
file-acl that always signals a file-error, or advising it to that
effect.





  reply	other threads:[~2022-06-06 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 14:43 bug#43723: 27.1; Errors in file-extended-attributes prevent from saving buffer Eli Zaretskii
2022-06-06 16:22 ` Lars Ingebrigtsen
2022-06-06 16:53   ` Eli Zaretskii [this message]
2022-06-07  9:26     ` Lars Ingebrigtsen
2022-06-07 11:35       ` Eli Zaretskii
2022-06-07 11:52         ` Lars Ingebrigtsen
2022-06-07 13:07           ` Eli Zaretskii
2022-06-07 18:04             ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8335gh91ip.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=43723@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).