From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: "Martin MOKREJŠ" <mmokrejs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: USB list <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 4.5.1: UBSAN: Undefined behaviour in ./arch/x86/include/asm/atomic.h:156:9
Date: Thu, 21 Apr 2016 19:48:00 +0900 [thread overview]
Message-ID: <20160421104800.GA6884@kroah.com> (raw)
In-Reply-To: <56e89573-3fb5-39cc-c330-e6f1c1c6c58f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, Apr 21, 2016 at 11:18:16AM +0200, Martin MOKREJŠ wrote:
> Hi Greg,
>
> thank you for your answer.
>
> Greg KH wrote:
> > On Thu, Apr 21, 2016 at 12:22:49AM +0200, Martin MOKREJŠ wrote:
> > > Hi,
> > > I am not certain to to forward this to, so I am trying linux-usb and ext4. Please add relevant people/lists, thank you.
> > >
> > > # dmesg | grep "UBSAN: Undefined behaviour"
> > > [ 2.638843] UBSAN: Undefined behaviour in drivers/usb/host/ehci-hub.c:873:47
> > > [ 8.553620] UBSAN: Undefined behaviour in fs/ext4/mballoc.c:2612:15
> > > [ 25.341048] UBSAN: Undefined behaviour in fs/ext4/mballoc.c:1274:11
> > > [ 41.460542] UBSAN: Undefined behaviour in ./arch/x86/include/asm/atomic.h:156:9
> > > #
> > >
> > > Full dmesg is attached.
> > >
> > > Hope this helps,
> > > Martin
> >
> > > [ 0.000000] Linux version 4.5.1-default-pciehp (root@vostro) (gcc version 5.3.0 (Gentoo 5.3.0 p1.0, pie-0.6.5) ) #1 SMP Thu Apr 14 14:17:48 CEST 2016
> >
> > Please try 4.6-rc4, a number of UBSAN issues have been fixed there.
>
> They are still present:
>
> # dmesg | grep "UBSAN: Undefined behaviour"
> [ 3.113405] UBSAN: Undefined behaviour in drivers/usb/host/ehci-hub.c:877:47
> [ 5.678949] UBSAN: Undefined behaviour in fs/ext4/mballoc.c:2619:15
> [ 18.345599] UBSAN: Undefined behaviour in fs/ext4/mballoc.c:1281:11
> [ 34.544363] UBSAN: Undefined behaviour in ./arch/x86/include/asm/atomic.h:156:9
Ah, sorry about that, turns out this is a bug in the tool, not in the
code, see the thread from a few weeks ago in the linux-usb archives with
the subject:
Subject: function ehci_hub_control in ehci-hub.c
for all of the details.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-21 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 22:22 4.5.1: UBSAN: Undefined behaviour in ./arch/x86/include/asm/atomic.h:156:9 Martin MOKREJŠ
[not found] ` <7d648a97-38f5-3d04-9ead-0b6e87088beb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-21 0:42 ` Greg KH
[not found] ` <20160421004229.GB10917-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2016-04-21 9:18 ` Martin MOKREJŠ
[not found] ` <56e89573-3fb5-39cc-c330-e6f1c1c6c58f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-21 10:48 ` Greg KH [this message]
[not found] ` <20160421104800.GA6884-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2016-04-21 11:17 ` Martin MOKREJŠ
[not found] ` <2121831c-e066-bb83-3b66-d3d3907064bf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-21 12:43 ` Greg KH
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=20160421104800.GA6884@kroah.com \
--to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mmokrejs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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