From: Randy Dunlap <rdunlap@xenotime.net>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: question: attribute 'require_context'
Date: Fri, 09 Sep 2011 17:54:34 -0700 [thread overview]
Message-ID: <4E6AB54A.1050504@xenotime.net> (raw)
In-Reply-To: <201109091747.18525.hartleys@visionengravers.com>
On 09/09/11 17:47, H Hartley Sweeten wrote:
> Hello all,
>
> I'm trying to do an allyesconfig build of the kernel on an old debian box
> with gcc version, gcc (Debian 4.3.2-1.1) 4.3.2. Everything goes fine until
> the DRBD device driver gets compiled. At that point I get a bunch of
> error messages like this:
>
> drivers/block/drbd/drbd_int.h:974:39 error: attribute 'require_context': unknown attribute
>
> It looks like this is due to the following:
>
> #ifdef __CHECKER__
> # define __protected_by(x) __attribute__((require_context(x,1,999,"rdwr")))
> # define __protected_read_by(x) __attribute__((require_context(x,1,999,"read")))
> # define __protected_write_by(x) __attribute__((require_context(x,1,999,"write")))
> # define __must_hold(x) __attribute__((context(x,1,1), require_context(x,1,999,"call")))
> #else
> # define __protected_by(x)
> # define __protected_read_by(x)
> # define __protected_write_by(x)
> # define __must_hold(x)
> #endif
>
> Is the require_context attribute something found in a later version of gcc?
No, it's a proposed change (patch) to sparse.
You can see all sparse mailing list messages about that patch and other
questions about it by searching the linux-sparse archives at marc.info:
http://marc.info/?l=linux-sparse&w=2&r=1&s=require_context&q=b
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-09-10 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 0:47 question: attribute 'require_context' H Hartley Sweeten
2011-09-10 0:54 ` Randy Dunlap [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=4E6AB54A.1050504@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
/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