All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: UBSAN: Undefined behaviour in drivers/usb/host/ehci-hub.c:877:47
Date: Thu, 12 May 2016 19:10:27 +0200	[thread overview]
Message-ID: <20160512171027.GA2925@kroah.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1605121924390.4797@math.ut.ee>

On Thu, May 12, 2016 at 07:38:00PM +0300, Meelis Roos wrote:
> I am seeing it on multiple different PC-s.
> 
> [    7.837957] ================================================================================
> [    7.837959] UBSAN: Undefined behaviour in drivers/usb/host/ehci-hub.c:877:47

And it's a bug in UBSAN, please see the email archives, it keeps coming
up.

sorry,

greg k-h

      reply	other threads:[~2016-05-12 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 16:38 UBSAN: Undefined behaviour in drivers/usb/host/ehci-hub.c:877:47 Meelis Roos
2016-05-12 17:10 ` Greg Kroah-Hartman [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=20160512171027.GA2925@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=stern@rowland.harvard.edu \
    /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.