From: Jeff Mahoney <jeffm@suse.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
arjan@linux.intel.com, reiserfs-devel@vger.kernel.org,
peterz@infradead.org
Subject: Re: [LOCKDEP linux-2.6.27-rc7] reiserfs circular locking
Date: Wed, 24 Sep 2008 17:18:35 -0400 [thread overview]
Message-ID: <48DAAEAB.50009@suse.com> (raw)
In-Reply-To: <20080924221425.3b4939ba@lxorguk.ukuu.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alan Cox wrote:
>> I have a reiserfs patch set that should address this. I haven't
>> submitted it recently because I'm chasing down a reiserfs bug report
>> that may or may not be related to the patch set.
>>
>> You can grab the patch set out of an opensuse kernel src rpm.
>
> Jeff: See also bugzilla.kernel.org #9136 which seems to match
>
> BTW - does anyone have a view where the existing reiserfs bugs should be
> assigned as they are currently assigned to namesys...
They're fine being assigned to the reiserfs development list, it's just
that the address in bko is wrong. The current address is
reiserfs-devel@vger.kernel.org.
I'll take this bug over, though.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkjarqsACgkQLPWxlyuTD7LCLQCdF5BDrD+cdYGlqFUZ+Pu5oi5/
aFsAnAhfHjv8oXjbR/zXTd1fuEa8abkj
=7ayP
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-09-24 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 18:39 [LOCKDEP linux-2.6.27-rc7] reiserfs circular locking Jesse Brandeburg
2008-09-24 18:55 ` Jeff Mahoney
2008-09-24 21:14 ` Alan Cox
2008-09-24 21:18 ` Jeff Mahoney [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=48DAAEAB.50009@suse.com \
--to=jeffm@suse.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=reiserfs-devel@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