• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Classify VNODE SCOPE actions for file operations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Classify VNODE SCOPE actions for file operations

  • Subject: Re: Classify VNODE SCOPE actions for file operations
  • From: sheetal phirke <email@hidden>
  • Date: Thu, 14 Apr 2011 13:03:24 +0530 (IST)

Thanks All for ur reply...


From all these reading I have clear following things :


1: First question to get filename at the time of KAUTH_VNODE_ADD_FILE:

This is a place to do authorization about  "Can I able to create a file in given directory?", but new file is not created yet so it is not possible to get newly created file name.



2: In second question I need to differentiate between open & read:

KAUTH_VNODE_READ_DATA is going to ask permission to read contents of file, so once we allow in case of open file, It is not going to ask again when we are going to read the file.


When I open any file (using terminal, programmatically, by finder etc.) I get different events like: (not only KAUTH_VNODE_READ_DATA)


  • Programmatically using open call

KAUTH_VNODE_READ_DATA (open in read mode)

KAUTH_VNODE_WRITE_DATA (open in write mode)


  • open in finder (using TextEditor)

Here I get many events like:

.

.


KAUTH_VNODE_WRITE_DATA | KAUTH_VNODE_ACCESS

KAUTH_VNODE_READ_DATA | KAUTH_VNODE_ACCESS

KAUTH_VNODE_EXECUTE_DATA | KAUTH_VNODE_ACCESS

KAUTH_VNODE_READ_DATA

.

.

  • open in finder (using Dashcode)

Here I get events somewhat same as using TestEditor, 


.

.

KAUTH_VNODE_WRITE_DATA | KAUTH_VNODE_ACCESS

KAUTH_VNODE_READ_DATA | KAUTH_VNODE_ACCESS

KAUTH_VNODE_EXECUTE_DATA | KAUTH_VNODE_ACCESS

.

.

following events are repeated when I open the file, trying to read, write or access in Dashcode, which is not in case of TextEditor, so the behavior is different.



How should I clear about file open events, so I can do particular activity when file is going to open. I have to also consider performance factor.



Thanks,

Sheetal.


From: Ken Hornstein <email@hidden>
To: email@hidden
Sent: Fri, 8 April, 2011 12:55:29 AM
Subject: Re: Classify VNODE SCOPE actions for file operations

>I think this discussion is probably moot anyway because even if you get
>a name, you can't depend on using it to find a vnode again (consider
>renaming, deleting, etc).
>You could use it for logging purposes I suppose.

Well, if you wanted to make a kauth decision based on the name (which I
admit is a bit weird to me, but hey, whatever), then you could use it
at that time.  The original poster wasn't exactly specific on what they
were interested in doing.

>True for KAUTH_VNODE_ADD_FILE - you have different combos of vnodes
>depending on the real operation.  The vfs may not be trying to create a
>file at all - see access1, rename.

I guess it really should be labelled "ADD_FILE_TO_DIRECTORY".

>I don't know about all filesystems, but HFS, Apple's SMB , Thursby's
>CIFS vfs return it.
>NFS doesn't, but I would bet that AFP does.  I know va_name is used by
>coreservicesd, and is how FSGetCatalogInfo calls get the 
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >Re: Classify VNODE SCOPE actions for file operations (From: Ken Hornstein <email@hidden>)

  • Prev by Date: Re: Bug in NFS
  • Next by Date: posix_memalign(&ptr, 32, 0 fails)
  • Previous by thread: Re: Classify VNODE SCOPE actions for file operations
  • Next by thread: Boot flags
  • Index(es):
    • Date
    • Thread