All of lore.kernel.org
 help / color / mirror / Atom feed
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:52:17 +0200	[thread overview]
Message-ID: <4E560D41.9020101@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75377B83D0@lisa.maurer-it.com>

On 8/25/2011 10:42 AM, Dietmar Maurer wrote:
>>> Are there known bugs with 131.6.1.el6 (rhel6.2 is still beta)?
>>
>> I am not sure I understand the question... kernel is kind of big and a query in
>> bugzilla.redhat.com will answer your question too :)
> 
> You suggested to use another kernel, so I thought you are aware of a specific bug related to old dlm_plock.c as used in  131.6.1.el6?

The new kernel has a plock fix that the old one does not have. Unless
you are using posix locks, it doesn?t affect you.

You need a new kernel to build the userland counterpart without workaround.

Fabio



  reply	other threads:[~2011-08-25  8:52 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
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 [this message]
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=4E560D41.9020101@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.