cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: mmotm 2009-01-14-20-31 uploaded (gfs2)
Date: Fri, 16 Jan 2009 17:37:07 +0000	[thread overview]
Message-ID: <1232127427.9571.589.camel@quoit> (raw)
In-Reply-To: <20090116093550.ce7229d5.akpm@linux-foundation.org>

Hi,

On Fri, 2009-01-16 at 09:35 -0800, Andrew Morton wrote:
> On Fri, 16 Jan 2009 09:06:23 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> 
> > >>> which is not ideal, but I don't see any easy way to avoid the #ifdef,
> > >>>
> > >> Take a look in fs.h:
> > >>
> > >> #define generic_setlease(a, b, c) ({ -EINVAL; })
> > >>
> > >> If that wasn't a stupid macro, your code would have compiled and ran
> > >> just as intended.
> > >>
> > > There doesn't seem to be an easy answer though. If I #define it to NULL,
> > > that upsets other parts of the code that rely on that macro, and if I
> > > turn it into a inline function which returns -EINVAL, then presumably I
> > > can't take its address for my file_operations.
> > 
> > No, gcc will allow &inline_func and out-of-line it if it is needed (AFAIK;
> > I've seen a few cases of that).
> > 
> 
> yup.  It measn that we'll get a separate private copy of the
> generic_setlease() code in each compilation unit which takes its
> address, but I don't think that would kill us.
> 
> The prevention is of course to put the stub function in a core kernel
> .c file and export it to modules.
> 
Ok, I'll have another look at this and try and cook something up,

Steve.




  reply	other threads:[~2009-01-16 17:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200901150432.n0F4WI66023742@imap1.linux-foundation.org>
2009-01-15 19:13 ` [Cluster-devel] Re: mmotm 2009-01-14-20-31 uploaded (gfs2) Randy Dunlap
2009-01-16 10:20   ` Steven Whitehouse
2009-01-16 16:43     ` Andrew Morton
2009-01-16 17:02       ` Steven Whitehouse
2009-01-16 17:06         ` Randy Dunlap
2009-01-16 17:35           ` Andrew Morton
2009-01-16 17:37             ` Steven Whitehouse [this message]
2009-01-19 15:16             ` Steven Whitehouse
2009-01-19 17:05               ` Randy Dunlap
2009-01-19 17:27                 ` Steven Whitehouse
2009-01-19 17:55                   ` Randy Dunlap

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=1232127427.9571.589.camel@quoit \
    --to=swhiteho@redhat.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).