posting POSIX draft ACL patches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



So, I've finally figured out how to use git format-patch. It took
me a lot of tries before I discovered all you do is specify "master.."
to make it work. (I still haven't tried to email them via gmail, but
I've found the doc for that.)

At this point, the patches are still in need of testing (I have yet to
test the nfsd case where file object creation specifies a POSIX draft
ACL, since neither FreeBSD nor Linux clients do that.)

Is it time to post the patch sets for others to try or should I wait a while?

A couple of questions...
The patches currently have a lot of dprintk()s I used for testing.
Should those be removed before posting or left in for now?

They are currently based on linux-6.11.0-rc6 (linux-next of a few
weeks ago). What do you guys do w.r.t. rebasing them?

There are three sets: common, client and server (common is
needed by both the others.
The other two sets implement client and server side for handling
the new attributes proposed in
https://datatracker.ietf.org/doc/draft-rmacklem-nfsv4-posix-acls/

Thanks in advance for any help, rick
ps: The problem I thought I had w.r.t. server side large ACLs does
      not appear to be a problem. It also appears that the nfsd always
       sets up a scratch buffer, so the server code doesn't do that, either.




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux