From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Confused about BUG_ON in rpcb_getport_async
Date: Wed, 13 Aug 2008 20:10:09 -0400 [thread overview]
Message-ID: <1218672609.9042.86.camel@localhost> (raw)
In-Reply-To: <18595.29231.61262.220929-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
On Thu, 2008-08-14 at 09:45 +1000, Neil Brown wrote:
> Just to confirm, you are saying that the current BUG_ON is indeed
> wrong, and the fact that it fires does not imply any real bug.
> It should be removed. Possibly a BUG_ON could be put somewhere else
> to catch incorrect behaviour.
>
> Is that correct?
Yes.
> I now have multiple people for whom this BUG_ON has fired.
Could you send us a trace? AFAIK it shouldn't really be happening...
Trond
next prev parent reply other threads:[~2008-08-14 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 2:27 Confused about BUG_ON in rpcb_getport_async Neil Brown
[not found] ` <18592.62730.840231.108375-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-08-12 20:32 ` Trond Myklebust
2008-08-13 23:45 ` Neil Brown
[not found] ` <18595.29231.61262.220929-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-08-14 0:10 ` Trond Myklebust [this message]
2008-08-14 2:26 ` Neil Brown
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=1218672609.9042.86.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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.