public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andreas Dilger <adilger@dilger.ca>,
	Anton Altaparmakov <anton@tuxera.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	Szabolcs Szakacsits <szaka@tuxera.com>,
	Janne Kalliom?ki <janne@tuxera.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Direct i/o changes break all non-GPL file systems
Date: Sat, 11 Feb 2012 08:18:44 -0800	[thread overview]
Message-ID: <m2mx8p738b.fsf@firstfloor.org> (raw)
In-Reply-To: <20120210211946.GJ23916@ZenIV.linux.org.uk> (Al Viro's message of "Fri, 10 Feb 2012 21:19:48 +0000")

Al Viro <viro@ZenIV.linux.org.uk> writes:

> and should not be used by any modules; don't export it at all
> 	3) it's a layering violation that unfortunately still is needed for
> an in-tree module.  The *only* case where I'd consider EXPORT_SYMBOL_GPL
> borderline useful, as a bad proxy for EXPORT_SYMBOL_DONT_USE_OUT_OF_TREE.

I had the namespace patches to make this explicit some time ago

http://lwn.net/Articles/259839/

This allows to export specific symbols only for special other modules,
in case it's only a single module that needs a "backdoor"

I can look at resubmitting the patchkit.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only

      reply	other threads:[~2012-02-11 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08  0:07 Direct i/o changes break all non-GPL file systems Anton Altaparmakov
2012-02-08  0:15 ` Alan Cox
2012-02-08  0:28   ` Anton Altaparmakov
2012-02-08  1:51     ` Andreas Dilger
2012-02-10 19:28       ` Linus Torvalds
2012-02-10 21:19         ` Al Viro
2012-02-11 16:18           ` Andi Kleen [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=m2mx8p738b.fsf@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=adilger@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anton@tuxera.com \
    --cc=hch@infradead.org \
    --cc=janne@tuxera.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szaka@tuxera.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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