netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: KY Srinivasan <kys@microsoft.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jason Wang <jasowang@redhat.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Daniel Borkmann <dborkman@redhat.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"David S. Miller" <davem@davemloft.net>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Sitsofe Wheeler <sitsofe@gmail.com>
Subject: Re: [hyperv] BUG at drivers/hv/channel.c:462 while changing MTU
Date: Mon, 25 Aug 2014 10:50:29 -0700	[thread overview]
Message-ID: <20140825175029.GA25551@kroah.com> (raw)
In-Reply-To: <cf94fd58947d4c5aa6d0d369c1126d7f@BY2PR0301MB0711.namprd03.prod.outlook.com>

On Mon, Aug 25, 2014 at 05:34:27PM +0000, KY Srinivasan wrote:
> 
> 
> > -----Original Message-----
> > From: Dan Carpenter [mailto:dan.carpenter@oracle.com]
> > Sent: Monday, August 25, 2014 2:37 AM
> > To: Sitsofe Wheeler
> > Cc: KY Srinivasan; Greg Kroah-Hartman; Jason Wang; linux-
> > kernel@vger.kernel.org; David S. Miller; Daniel Borkmann;
> > netdev@vger.kernel.org; devel@linuxdriverproject.org; Haiyang Zhang
> > Subject: Re: [hyperv] BUG at drivers/hv/channel.c:462 while changing MTU
> > 
> > The code here is:
> > 
> > drivers/hv/channel.c
> >    460          BUG_ON(ret != 0);
> >    461          t = wait_for_completion_timeout(&info->waitevent, 5*HZ);
> >    462          BUG_ON(t == 0);
> > 
> > So it calls BUG_ON() if the teardown takes more than 5 seconds.  It's most
> > likely that there is a race condition somewhere.  It's also possible that it's just
> > taking longer than 5 seconds for some odd reason and the bug would go
> > away if we raised it to 60 seconds.
> > 
> > BUG_ON() after 5 seconds seems like a very aggressive thing.
> 
> Dan,
> 
> I am going to audit all BUG_ON() instances.

Please remove them all, no kernel driver should ever crash the kernel
and not give a user a chance to recover :(

thanks,

greg k-h

  reply	other threads:[~2014-08-25 17:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 12:36 [hyperv] BUG at drivers/hv/channel.c:462 while changing MTU Sitsofe Wheeler
2014-08-19 21:29 ` Haiyang Zhang
2014-08-20  3:41   ` Sitsofe Wheeler
2014-08-25 10:48     ` Richard Weinberger
2014-08-25 14:53       ` KY Srinivasan
2014-08-25 15:07         ` Richard Weinberger
2014-08-25 17:29           ` KY Srinivasan
2014-08-25  9:36 ` Dan Carpenter
2014-08-25 17:34   ` KY Srinivasan
2014-08-25 17:50     ` Greg Kroah-Hartman [this message]
2014-08-25 18:05       ` KY Srinivasan
2014-08-25 21:43   ` Sitsofe Wheeler
2014-08-25 21:48     ` KY Srinivasan
2014-08-27  9:33       ` Sitsofe Wheeler

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=20140825175029.GA25551@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sitsofe@gmail.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 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).