OpenVZ Forum - RDF feed
type: channel
items: Re: [PATCH] Send quota messages via netlink

Re: [PATCH] Send quota messages via netlink
type: item
description: Quoting Jan Kara (jack@suse.cz): > On Tue 04-09-07 16:32:10, Serge E. Hallyn wrote: > > Quoting Jan Kara (jack@suse.cz): > > > On Thu 30-08-07 17:14:47, Serge E. Hallyn wrote: > > > > Quoting Jan Kara (jack@suse.cz): > > > > > I imagine it so that you have a machine and on it several virtual > > > > > machines which are sharing a filesystem (or it could be a cluster). Now you > > > > > want UIDs to be independent between these virtual machines. That's it, > > > > > right? > > > > > Now to continue the example: Alice has UID 100 on machineA, Bob has > > > > > UID 100 on machineB. These translate to UIDs 1000 and 1001 on the common > > > > > filesystem. Process of Alice writes to a file and Bob becomes to be over > > > > > quota. In this situation, there would be probably two processes (from > > > > > machineA and machineB) listening on the netlink socket. We want to send a > > > > > message so that on Alice's desktop we can show a message: "You caused > > > > > Bob to exceed his quotas" and of Bob's desktop: "Alice has caused that you > > > > > are over quota.". > > > > > > > > Since this is over NFS, you handle it the way you would any other time > > > > that user Alice on some other machine managed to do this. > > > I meant this would actually happen over a local filesystem (imagine > > > something like "hostfs" from UML). > > > > Ok, then that is where I was previously suggesting that we use an api to > > report a uid meaningful in bob's context, where we currently (in the > > absense of meaningful mount uids and uid equivalence) tell Bob that root > > was the one who brought him over quota. From a user pov 'nobody' would > > make more sense, but I don't think we want the kernel to know about user > > nobody, right? > But what is the problem with using the filesystem ids? All virtual > machines in my example should have a notion of those... I don't know what you mean by filesystem ids. Do you mean the uid stored on the fs? I imagine a network fs could get fancy an…
creator: serge
date: 2007-09-04T23:48:52-00:00

Re: [PATCH] Send quota messages via netlink
type: item
description: On Tue 04-09-07 18:48:52, Serge E. Hallyn wrote: > Quoting Jan Kara (jack@suse.cz): > > On Tue 04-09-07 16:32:10, Serge E. Hallyn wrote: > > > Quoting Jan Kara (jack@suse.cz): > > > > On Thu 30-08-07 17:14:47, Serge E. Hallyn wrote: > > > > > Quoting Jan Kara (jack@suse.cz): > > > > > > I imagine it so that you have a machine and on it several virtual > > > > > > machines which are sharing a filesystem (or it could be a cluster). Now you > > > > > > want UIDs to be independent between these virtual machines. That's it, > > > > > > right? > > > > > > Now to continue the example: Alice has UID 100 on machineA, Bob has > > > > > > UID 100 on machineB. These translate to UIDs 1000 and 1001 on the common > > > > > > filesystem. Process of Alice writes to a file and Bob becomes to be over > > > > > > quota. In this situation, there would be probably two processes (from > > > > > > machineA and machineB) listening on the netlink socket. We want to send a > > > > > > message so that on Alice's desktop we can show a message: "You caused > > > > > > Bob to exceed his quotas" and of Bob's desktop: "Alice has caused that you > > > > > > are over quota.". > > > > > > > > > > Since this is over NFS, you handle it the way you would any other time > > > > > that user Alice on some other machine managed to do this. > > > > I meant this would actually happen over a local filesystem (imagine > > > > something like "hostfs" from UML). > > > > > > Ok, then that is where I was previously suggesting that we use an api to > > > report a uid meaningful in bob's context, where we currently (in the > > > absense of meaningful mount uids and uid equivalence) tell Bob that root > > > was the one who brought him over quota. From a user pov 'nobody' would > > > make more sense, but I don't think we want the kernel to know about user > > > nobody, right? > > But what is the problem with using the filesystem ids? All virtual > > machines in my example should have a notion of those... > > I don't kn…
creator: Jan Kara
date: 2007-09-05T13:32:01-00:00