From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 55971] New: redefined error in 2.6.32-279.22.1.el6.x86_64 kernel
Date: Sat, 30 Mar 2013 07:32:00 +0000 (UTC) [thread overview]
Message-ID: <bug-55971-58281@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=55971
Summary: redefined error in 2.6.32-279.22.1.el6.x86_64 kernel
Product: Backports project
Version: unspecified
Kernel Version: 2.6.32-279.22.1.el6.x86_64
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Compat
AssignedTo: backports@vger.kernel.org
ReportedBy: sihara@ddn.com
Regression: No
Since RHEL6.3's security updated kernel (2.6.32-279.22.1.el6.x86_64) has
included two macros (rcu_dereference_protected and kfree_rcu) in
include/linux/rcupdate.h
These were not existed in original RHEL6.3's kernel (2.6.32-279) and even the
previous kernel of 2.6.32-279.22.1.el6.x86_64.
The other hand, these macros are defined in include/linux/compat-x.z.h.
(rcu_dereference_protected in compat-2.6.34.h and kfree_rcu in compat-3.0.h).
It needs to check in compat headers wether these macro are defined or not,
doesn't it now? otherwise we see redefined error if both kernel header and
compat headers are included for the souce codes..
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-03-30 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 7:32 bugzilla-daemon [this message]
2013-03-31 0:58 ` [Bug 55971] redefined error in 2.6.32-279.22.1.el6.x86_64 kernel bugzilla-daemon
2013-04-03 14:31 ` bugzilla-daemon
2013-04-03 21:15 ` bugzilla-daemon
2013-04-03 21:16 ` bugzilla-daemon
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=bug-55971-58281@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.