Hello!
As we discussed 2 months ago, dazuko could use d_path when running on an
Linux 2.6 SMP system and __d_path is not exported. I have now implemented
that change as you specified (behaviour changes only for Linux 2.6 SMP
chrooted processes). [see attached email]
I have uploaded the patch to Savannah:
https://savannah.nongnu.org/patch/index.php?func=detailitem&item_id=4602
I hope you find it to your liking and include it into Dazuko source.
--
Sami Tikka tel. +358 9 2520 5115
senior software engineer fax. +358 9 2520 5014
mobile +358 40 7379388
F-Secure Corporation http://www.f-secure.com
BE SURE
--- Begin Message ---
Tikka, Sami wrote:
> Dazuko could use the exported d_path. Then the filename the driver reports
> will be relative to the current root of the process that made the file
> access. But this is not a problem. The process which gets the dazuko events
> can easily check readlink /proc/PID/root and prepend that to the filename
in
> the event.
>
> What do you think, John? Could you make dazuko use d_path on Linux?
Well, this would double the amount of user/kernel switches, which would be a
performance hit. It would also require that the /proc system is available.
But yes, this would work.
If I were to implement this for Linux 2.6 SMP (the only affected kernels),
then I would change Dazuko to send a filename without the beginning "/" for
files in chroot'd environments. This would signal the user application that
it needed to do a lookup for the full path. This would reduce the extra
overhead to *only* file accesses in a chroot environment.
With DazukoFS we won't have this problem because we won't need __d_path().
But we can use this hack until DazukoFS is available.
This hack would only be required for Linux 2.6 SMP kernels that do not
export __d_path().
John Ogness
--
Dazuko Maintainer
--- End Message ---
_______________________________________________
Dazuko-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/dazuko-devel
