All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] 2.6.36-rc6-git4 - dlm/lockfs - general protection fault
Date: Thu, 7 Oct 2010 11:25:29 +0200	[thread overview]
Message-ID: <20101007092528.GA6673@develbox.linuxbox.cz> (raw)
In-Reply-To: <1286357641.2696.4.camel@dolmen>

> This looks like a configfs issue (copying in the maintainer), and since
> it is rmdir, I'm guessing that this is during dlm lockspace removal. It
> doesn't look from the trace as if it has got as far as the dlm code at
> the point at which the problem occurs,
> 
> Steve.

Hello Steve and thanks for the reply. Thanks, even though I've already
had joel CCed ;)
I wonder whether I should create bugzilla entry and if yes, where?
Since it's certainly configfs problem and it doesn't have it's own
bugzilla, maybe I should use kernel bugzilla?
nik



>  
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis at linuxbox.cz
-------------------------------------



WARNING: multiple messages have this Message-ID (diff)
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
	nikola.ciprich@linuxbox.cz, cluster-devel@redhat.com,
	Joel Becker <joel.becker@oracle.com>
Subject: Re: [Cluster-devel] 2.6.36-rc6-git4 - dlm/lockfs - general protection fault
Date: Thu, 7 Oct 2010 11:25:29 +0200	[thread overview]
Message-ID: <20101007092528.GA6673@develbox.linuxbox.cz> (raw)
In-Reply-To: <1286357641.2696.4.camel@dolmen>

> This looks like a configfs issue (copying in the maintainer), and since
> it is rmdir, I'm guessing that this is during dlm lockspace removal. It
> doesn't look from the trace as if it has got as far as the dlm code at
> the point at which the problem occurs,
> 
> Steve.

Hello Steve and thanks for the reply. Thanks, even though I've already
had joel CCed ;)
I wonder whether I should create bugzilla entry and if yes, where?
Since it's certainly configfs problem and it doesn't have it's own
bugzilla, maybe I should use kernel bugzilla?
nik



>  
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

  reply	other threads:[~2010-10-07  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06  8:50 [Cluster-devel] 2.6.36-rc6-git4 - dlm/lockfs - general protection fault Nikola Ciprich
2010-10-06  8:50 ` Nikola Ciprich
2010-10-06  9:34 ` [Cluster-devel] " Steven Whitehouse
2010-10-06  9:34   ` Steven Whitehouse
2010-10-07  9:25   ` Nikola Ciprich [this message]
2010-10-07  9:25     ` Nikola Ciprich

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=20101007092528.GA6673@develbox.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    /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.