bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Ondrej Valousek <ondrej.valousek.xm@renesas.com>
To: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>
Cc: "bug-gnulib@gnu.org" <bug-gnulib@gnu.org>
Subject: RE: [PATCH] Basic support for checking NFSv4 ACLs in Linux
Date: Wed, 16 Nov 2022 09:51:46 +0000	[thread overview]
Message-ID: <TYXPR01MB1854BAFA66C76EAAE952ECC7D9079@TYXPR01MB1854.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAHpGcMLD3UMSxf-0m3Nt9AK7EKJpAfdmT93cKTnq4r4Rzu_W0A@mail.gmail.com>


> I'm not really sure what to do about ACE4_READ_NAMED_ATTRS and ACE4_WRITE_NAMED_ATTRS; those are not the same as Linux extended attributes. This will need a bit of testing against various NFSv4 servers to give reasonable results.

Can we just commit the code as-is without the extra mask checks for now?
Frankly speaking:
- I still do not understand why we should be doing it, I perceive it as an unnecessary extra potentially fragile code
- the existing code just "works" well to me. Tried various scenarios on Netapp and Linux NFS server. It just works.
- I understand it might not be perfect, but I think even you will agree that it's far better than what we have now in there (i.e. nothing)
- since most of the heavy lifting has already been done, we can patch the masks later on (if needed) as it should be fairly easy job once we know exactly what to do there.

I am happy to incorporate the other suggestions you had (thanks for them), but I have reached the point that I can't invest more time into it.
Thanks,

Ondrej

  reply	other threads:[~2022-11-16  9:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  8:16 [PATCH] Basic support for checking NFSv4 ACLs in Linux Ondrej Valousek
2022-11-14 12:49 ` Andreas Grünbacher
2022-11-15  9:17   ` Ondrej Valousek
2022-11-15 12:24     ` Andreas Grünbacher
2022-11-15 12:35     ` Andreas Grünbacher
2022-11-15 12:46       ` Ondrej Valousek
2022-11-15 13:14         ` Andreas Grünbacher
2022-11-16  9:51           ` Ondrej Valousek [this message]
2022-11-15  2:45 ` Paul Eggert
2022-11-15  7:00   ` Andreas Grünbacher
  -- strict thread matches above, loose matches on Subject: below --
2022-12-02 12:40 Ondrej Valousek
2022-12-02 13:33 ` Bruno Haible
2022-12-22 17:04 ` Bruno Haible
2022-12-23 23:32   ` Paul Eggert
2022-12-24 13:00     ` Ondrej Valousek
2022-12-24 19:27       ` Paul Eggert
2022-12-28  4:13     ` Paul Eggert
2022-12-28  9:07       ` Ondrej Valousek
2022-12-28 17:09         ` Paul Eggert
2022-12-01 14:24 Ondrej Valousek
2022-12-02  0:58 ` Bruno Haible
2022-12-01  9:50 Ondrej Valousek
2022-12-01 11:52 ` Bruno Haible
2022-11-24 17:08 Ondrej Valousek
2022-11-25  2:46 ` Bruno Haible
2022-11-25  9:34 ` Andreas Grünbacher
2022-11-25 10:17   ` Andreas Grünbacher
2022-11-28  7:29     ` Ondrej Valousek
2022-11-29 10:58       ` Andreas Grünbacher
     [not found] <20221109152951.1003859-1-ondrej.valousek.xm@renesas.com>
     [not found] ` <CAHpGcM+=+9Qp1umqzmP-aXHbEPtu8xB_hYP6kNk8UY52WOXpKA@mail.gmail.com>
     [not found]   ` <TY1PR01MB1850006B3019A6BA823B5859D9019@TY1PR01MB1850.jpnprd01.prod.outlook.com>
     [not found]     ` <CAHpGcMKSM7Sgc3jnexdRSajFhC8q0pTcg+M7LNpJs8cMRBgjqQ@mail.gmail.com>
2022-11-11  8:40       ` Ondrej Valousek
2022-11-13 19:32         ` Paul Eggert
2022-11-09 15:32 Ondrej Valousek
2022-10-27  9:34 Ondrej Valousek
2022-10-27 19:52 ` Bruno Haible
2022-10-28 14:33   ` Ondrej Valousek
2022-10-30 18:36     ` Paul Eggert
2022-10-31  8:05       ` Ondrej Valousek
2022-10-31 19:36         ` Paul Eggert
2022-11-07 12:45           ` Ondrej Valousek
2022-11-08 22:11             ` Andreas Grünbacher

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=TYXPR01MB1854BAFA66C76EAAE952ECC7D9079@TYXPR01MB1854.jpnprd01.prod.outlook.com \
    --to=ondrej.valousek.xm@renesas.com \
    --cc=andreas.gruenbacher@gmail.com \
    --cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).