From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Problems with [PATCH] dlm_controld: fix plock dev_write no op
Date: Thu, 25 Aug 2011 10:16:05 +0200 [thread overview]
Message-ID: <4E5604C5.1060803@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75377B71D8@lisa.maurer-it.com>
On 8/25/2011 7:10 AM, Dietmar Maurer wrote:
>> On 8/24/2011 8:18 AM, Dietmar Maurer wrote:
>>> Compile is broken after that patch. I get:
>>>
>>> /cluster-3.1.5/group/dlm_controld/plock.c:744:2: warning: #warning
>> DLM_PLOCK_FL_CLOSE undefined. Enabling build workaround.
>>> /cluster-3.1.5/group/dlm_controld/plock.c: In function
>> \u2018process_plocks\u2019:
>>> /cluster-3.1.5/group/dlm_controld/plock.c:1595: error: \u2018struct
>>> dlm_plock_info\u2019 has no member named \u2018flags\u2019
>>> make[2]: *** [plock.o] Error 1
>>> make[2]: Leaving directory `/home/dietmar/pve2-devel/redhat-cluster-
>> pve/cluster-3.1.5/group/dlm_controld'
>>> make[1]: *** [all] Error 2
>>>
>>> - Dietmar
>>>
>>>
>>
>> I pushed a workaround for this, but you need to update your kernel headers.
>
> Well, I use headers from recent RHEL6 kernel (131.6.1.el6).
>
> Is that fixed in newer RHEL6 kernels or what kernel version do you suggest?
You need kernel from RHEL6.2.
Fabio
next prev parent reply other threads:[~2011-08-25 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 5:10 [Cluster-devel] Problems with [PATCH] dlm_controld: fix plock dev_write no op Dietmar Maurer
2011-08-25 8:16 ` Fabio M. Di Nitto [this message]
2011-08-25 8:29 ` Dietmar Maurer
2011-08-25 8:32 ` Fabio M. Di Nitto
2011-08-25 8:42 ` Dietmar Maurer
2011-08-25 8:52 ` Fabio M. Di Nitto
2011-08-25 9:09 ` Dietmar Maurer
-- strict thread matches above, loose matches on Subject: below --
2011-08-24 6:55 Dietmar Maurer
2011-08-24 6:18 Dietmar Maurer
2011-08-24 6:39 ` Fabio M. Di Nitto
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=4E5604C5.1060803@redhat.com \
--to=fdinitto@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 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.