public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.7
Date: Mon, 09 Nov 2015 10:09:00 -0000	[thread overview]
Message-ID: <20151109100953.GA20001@calimero.vinschen.de> (raw)
In-Reply-To: <87fv0ihqfk.fsf@Rainer.invalid>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

On Nov  6 20:35, Achim Gratz wrote:
> Corinna Vinschen writes:
> > One of the sore points is performance hit when
> > using AuthZ to fetch the effective user permissions.  How's your
> > impression?  Is it noticable in your environment?
> 
> Aside from the somewhat contrived example I already gave, the normal
> day-to-day operation with the snapshot so far was uneventful.  Other
> users besides me have the snapshot installed since about a week, so if
> there were any catastrophic degradation I should know by now (I did ask
> them to report back if they see something that's different as before).

Sounds good.  Nevertheless, I'll release 2.3.0-1 and an 2.4.0-0.1 test
release today.

It occured to me that there's a potential way to tweak the code to
reduce the number of AuthZ calls.  Consider:

If the user has its own ACE, and if user_perms | all_group_perms |
other_perms == user_perms, or if user_perms are already RWX, then there
are no groups which could have more permissions than the user already
owns all by itself.

Good examples of this scenario are typical default POSIX perms 644 or
755 or even 775, used a lot throughout existing Cygwin trees.  None of
them require to check with AuthZ, but the AuthZ test is performed
indiscriminately if it's a not one of the "new" Cygwin ACLs.

I'll look into that this week.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-09 10:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 10:09 Corinna Vinschen
2015-11-06 11:12 ` Marco Atzeri
2015-11-06 12:50   ` Corinna Vinschen
2015-11-06 14:51     ` Ken Brown
2015-11-06 19:35     ` Achim Gratz
2015-11-09 10:09       ` Corinna Vinschen [this message]
2015-11-06 16:30 ` Lemke, Michael  ST/HZA-ZIC2
2015-11-06 17:08   ` Corinna Vinschen

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=20151109100953.GA20001@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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).