linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Andrew Clayton <andrew@digital-domain.net>,
	Daniel J Blueman <daniel.blueman@gmail.com>,
	Dave Kleikamp <shaggy@austin.ibm.com>,
	jfs-discussion@lists.sourceforge.net,
	Andy Whitcroft <apw@shadowen.org>,
	sct@redhat.com, adilger@clusterfs.com,
	linux-ext4@vger.kernel.org, linux-acpi@vger.kernel.org,
	Len Brown <lenb@kernel.org>, Chuck Ebbert <cebbert@redhat.com>,
	dth <dth@dth.net>, Neil Brown <neilb@suse.de>
Subject: Re: [2/4] 2.6.23-rc6: known regressions
Date: Fri, 14 Sep 2007 13:21:25 -0400	[thread overview]
Message-ID: <20070914172124.GA2419@fieldses.org> (raw)
In-Reply-To: <46E81ACE.6030305@googlemail.com>

On Wed, Sep 12, 2007 at 06:58:54PM +0200, Michal Piotrowski wrote:
> Subject         : [NFSv4] 2.6.23-rc4 oops in nfs4_cb_recall
> References      : http://lkml.org/lkml/2007/9/4/53
>                   http://bugzilla.kernel.org/show_bug.cgi?id=9003
> Last known good : ?
> Submitter       : Daniel J Blueman <daniel.blueman@gmail.com>
> Caused-By       : ?
> Handled-By      : ?
> Workaround      : http://bugzilla.kernel.org/attachment.cgi?id=12797
> Status          : unknown

I have patches which fix this, which we're testing.  (See bugzilla.)
It's a long-standing bug, not a regression.

> Subject         : [NFSD OOPS] 2.6.23-rc1-git10
> References      : http://lkml.org/lkml/2007/8/2/462
> Last known good : ?
> Submitter       : Andrew Clayton <andrew@digital-domain.net>
> Caused-By       : ?
> Handled-By      : ?
> Status          : unknown

Neil's working on this.  Also not a regression.

--b.

      parent reply	other threads:[~2007-09-14 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46E8187E.9000006@googlemail.com>
2007-09-12 16:58 ` [2/4] 2.6.23-rc6: known regressions Michal Piotrowski
2007-09-12 16:58 ` Michal Piotrowski
     [not found] ` <46E81ACE.6030305@googlemail.com>
2007-09-12 17:36   ` Andy Whitcroft
2007-09-13 12:18   ` [Jfs-discussion] " Dave Kleikamp
2007-09-19 11:44     ` Oliver Neukum
2007-09-19 12:36       ` Dave Kleikamp
2007-09-14 16:51   ` Kamalesh Babulal
2007-09-14 17:21   ` J. Bruce Fields [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=20070914172124.GA2419@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=adilger@clusterfs.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew@digital-domain.net \
    --cc=apw@shadowen.org \
    --cc=cebbert@redhat.com \
    --cc=daniel.blueman@gmail.com \
    --cc=dth@dth.net \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=sct@redhat.com \
    --cc=shaggy@austin.ibm.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).