From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: Jeff Layton <jlayton@poochiereds.net>,
hch@infradead.org, linux-fsdevel@vger.kernel.org,
Dyno Hongjun Fu <hfu@vmware.com>
Subject: Re: Re: vfs: getname() / putname() used by VMware drivers
Date: Thu, 18 Sep 2014 10:00:55 -0700 [thread overview]
Message-ID: <20140918170055.GB14809@core.coreip.homeip.net> (raw)
In-Reply-To: <1611991.EqHGTGGzrk@storm>
On Thu, Sep 18, 2014 at 03:48:03PM +0200, Thomas Jarosch wrote:
> Hi Dmitry,
>
> On Monday, 15. September 2014 08:28:33 Dmitry Torokhov wrote:
> > >> As Christoph says...no, there's no way that we'll revert that.
> > >>
> > >> Those functions have hooks into the audit layer and 3rd party modules
> > >> almost universally got their usage wrong.
> > >
> > >thanks for the explanation, especially about the audit layer part.
> >
> > You do not need neither vmsync nor vmblock on kernels past 3.0 so just
> > hack around vmware-coonfig-tools.pl (or whatever the install script is
> > called) and do not compile them.
>
> thanks for the hint, that makes things a lot easier.
>
> Probably a lot of people on the web could stop to publish
> compiling-but-more-or-less-working patches to port
> those modules to recent kernels ;)
Yeah. Well, it is hard for VMware to go back and adjust already released
tools packages ;). I believe this issue is fixed in newer versions and in
open-vm-tools.
BTW, more and more distributions package open-vm-tools and I believe most of
the needed kernel drivers are now in mainline so things should be getting
better.
Thanks.
--
Dmitry
prev parent reply other threads:[~2014-09-18 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 13:57 vfs: getname() / putname() used by VMware drivers Thomas Jarosch
2014-09-12 22:11 ` Christoph Hellwig
2014-09-13 2:12 ` Jeff Layton
2014-09-15 7:41 ` Thomas Jarosch
2014-09-15 15:28 ` Dmitry Torokhov
2014-09-18 13:48 ` Thomas Jarosch
2014-09-18 17:00 ` Dmitry Torokhov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140918170055.GB14809@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=hch@infradead.org \
--cc=hfu@vmware.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=thomas.jarosch@intra2net.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).