Bernd Schemmer wrote: > Hi, > > (second try; my email to the list seems to got lost) > > Using sloggi (http://www.roqe.org/sloggi/ <http://www.roqe.org/sloggi/>) I > can change the output of uname for all zones (including the global zone) from > within a zone: > > global zone [Mon Dec 31 17:36:11 [EMAIL PROTECTED] > /export/install/profiles/sol3] > # uname -a > SunOS sol9 5.11 snv_78 sun4u sparc sun4u > > sunstudio12 zone [Mon Dec 31 17:36:23 [EMAIL PROTECTED] /] > # uname -a > SunOS sunstudio12 5.11 snv_78 sun4u sparc sun4u > > gcc zone [Mon Dec 31 17:37:12 [EMAIL PROTECTED] /] > # uname -a > SunOS gcc 5.11 snv_78 sun4u sparc sun4u > > sunstudio12 zone [Mon Dec 31 17:37:34 [EMAIL PROTECTED] /] > # slogctl -s MyOS > MyOS sol9 5.11 snv_78 sun4u > > sunstudio12 zone [Mon Dec 31 17:37:37 [EMAIL PROTECTED] /] > # uname -a > MyOS sol9 5.11 snv_78 sun4u sparc sun4u > > gcc zone [Mon Dec 31 17:37:18 [EMAIL PROTECTED] /] > # uname -a > MyOS sol9 5.11 snv_78 sun4u sparc sun4u > > global zone [Mon Dec 31 17:36:12 [EMAIL PROTECTED] > /export/install/profiles/sol3] > # uname -a > MyOS sol9 5.11 snv_78 sun4u sparc sun4u > > > The sloggi module was installed before creating the zones; the zones are all > sparse zones. > > I think this is a bug.
I looked at the source for this and it certainly looks like a bug in the way the sloggi kernel module is implemented. If you install this broken kernel module from the global zone then you'll open up this hole. You can't install random stuff into the kernel and expect things to keep working correctly. In this case, this kernel module interposes on the uname syscall and changes the behavior from the standard implementation. The uname syscall is allowed in all zones since there is no side-effect but this new kernel module introduces a side effect which leads to the bug. You might file a bug with whoever owns sloggi asking them to make the code zone aware. Jerry hole. _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
