This is not a problem, because compilation with CONFIG_VE=n deadly broken (by design)
On Sat, Aug 7, 2010 at 2:01 AM, Kirill Kolyshkin <[email protected]> wrote: > Plaza reply @ devel list > > sent from my google nexus one android mobile phone > > ---------- Forwarded message ---------- > From: "Dennis Schridde" <[email protected]> > Date: Aug 7, 2010 12:59 AM > Subject: [Devel] VZ_QUOTA without VE > To: <[email protected]> > > Hello! > > I am looking at the 2.6.32 branch: > Is it intentional that e.g. > VZ_QUOTA can be enabled even if VE is not? > > Particularly problematic seems > this: > struct proc_dir_entry *proc_vz_dir; > struct proc_dir_entry > *glob_proc_vz_dir; > > That's in kernel/ve/veowner.c (including > initialisation), but the quota code makes use of these variables. > So for > VZ_QUOTA and VE to be truly independent, the initialisation (as well as the > symbol itself) would have to move out of veowner.c into some "neutral" space > (imo). > > --Dennis > _______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
