From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Max Staudt <max@enpas.org>, David Sterba <dsterba@suse.com>
Cc: linux-fsdevel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] fs/affs: Fix basic permission bits to actually work
Date: Fri, 25 Sep 2020 12:07:22 +0200 [thread overview]
Message-ID: <c96b8ee5-5e96-07fd-de69-ffaa2a4f3bc6@physik.fu-berlin.de> (raw)
In-Reply-To: <20200827154900.28233-1-max@enpas.org>
Hi Max!
On 8/27/20 5:49 PM, Max Staudt wrote:
> The basic permission bits (protection bits in AmigaOS) have been broken
> in Linux' affs - it would only set bits, but never delete them.
> Also, contrary to the documentation, the Archived bit was not handled.
>
> Let's fix this for good, and set the bits such that Linux and classic
> AmigaOS can coexist in the most peaceful manner.
>
> Also, update the documentation to represent the current state of things.
Has there already been any progress on reviewing this?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-09-25 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 15:49 [PATCH] fs/affs: Fix basic permission bits to actually work Max Staudt
2020-08-27 15:51 ` John Paul Adrian Glaubitz
2020-08-31 9:38 ` David Sterba
2020-09-25 10:07 ` John Paul Adrian Glaubitz [this message]
2020-09-25 16:21 ` Max Staudt
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=c96b8ee5-5e96-07fd-de69-ffaa2a4f3bc6@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dsterba@suse.com \
--cc=geert@linux-m68k.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=max@enpas.org \
--cc=stable@vger.kernel.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.
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 NNTP newsgroup(s).