From: "Darrick J. Wong" <djwong@kernel.org>
To: Matthew Broomfield <mattysweeps@google.com>
Cc: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/375: clarify flipping the write bit
Date: Mon, 16 Sep 2024 14:18:12 -0700 [thread overview]
Message-ID: <20240916211812.GA182183@frogsfrogsfrogs> (raw)
In-Reply-To: <CALEiSPwGymqrBDiQ0sH1Vwmg9uzJ4KBe5tWx+BA_Vv4p0gvj_Q@mail.gmail.com>
On Sat, Sep 14, 2024 at 01:18:03PM -0700, Matthew Broomfield wrote:
> On Thu, Aug 1, 2024 at 4:04 PM Matthew Broomfield
> <mattysweeps@google.com> wrote:
> >
> > When checking if SGID is cleared upon chmod / setfacl the write bit is
> > flipped just to make sure permission changes are happening. This is
> > orthogonal to testing SGID.
> >
> > Added this information to the test description.
> >
> > Signed-off-by: Matthew Broomfield <mattysweeps@google.com>
> > ---
> > tests/generic/375 | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/tests/generic/375 b/tests/generic/375
> > index eb675144..44670350 100755
> > --- a/tests/generic/375
> > +++ b/tests/generic/375
> > @@ -7,6 +7,9 @@
> > # Check if SGID is cleared upon chmod / setfacl when the owner is not in the
> > # owning group.
> > #
> > +# The test flips the write bit to easily observe that chmod / setfacl are
> > +# successful. This is unrelated to testing SGID.
> > +#
> > . ./common/preamble
> > _begin_fstest auto quick acl perms
> >
> > --
> > 2.46.0.rc2.264.g509ed76dc8-goog
> >
>
> Hello, can someone review if the comment in this patch is accurate?
> Thanks in advance for your time.
I don't understand this new comment -- "flipping the write bit" is what
the chmod does, and that's what clears setgid.
--D
prev parent reply other threads:[~2024-09-16 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 23:04 [PATCH] generic/375: clarify flipping the write bit Matthew Broomfield
2024-09-14 20:18 ` Matthew Broomfield
2024-09-16 21:18 ` Darrick J. Wong [this message]
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=20240916211812.GA182183@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=mattysweeps@google.com \
--cc=zlang@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