linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Adam Morrison <mad@cs.technion.ac.il>
To: M G Berberich <berberic@fmi.uni-passau.de>
Cc: Nadav Amit <nadav.amit@gmail.com>,
	iommu@lists.linux-foundation.org,
	USB list <linux-usb@vger.kernel.org>,
	linux-mm@kvack.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code]
Date: Mon, 13 Jun 2016 16:11:39 +0300	[thread overview]
Message-ID: <CAHMfzJktLSPZuLJ0R90Zaa6tj+awX9NDO2DPzjxEEJuY0CFV+g@mail.gmail.com> (raw)
In-Reply-To: <20160613130651.GA8662@invalid>

Hi,

On Mon, Jun 13, 2016 at 4:06 PM, M G Berberich
<berberic@fmi.uni-passau.de> wrote:

> Hello,
>
>> >> With 4.7-rc2, after detecting a USB Mass Storage device
>> >>
>> >>  [   11.589843] usb-storage 4-2:1.0: USB Mass Storage device detected
>> >>
>> >> a constant flow of kernel-BUGS is reported (several per second).
>
> […]
>
>> > This looks like a bug in the memory management subsystem.  It should be
>> > reported on the linux-mm mailing list (CC'ed).
>>
>> This bug is IOMMU related (mailing list CC’ed) and IIUC already fixed.
>
> Not fixed in 4.7-rc3

These patches should fix the issue:

    https://lkml.org/lkml/2016/6/1/310
    https://lkml.org/lkml/2016/6/1/311

I'm not sure why they weren't applied... will ping the maintainers.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-06-13 13:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160609172444.GB6277@invalid>
2016-06-09 18:14 ` Alan Stern
2016-06-09 19:10   ` Nadav Amit
2016-06-13 13:06     ` M G Berberich
2016-06-13 13:11       ` Adam Morrison [this message]
2016-06-14  9:08         ` M G Berberich

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=CAHMfzJktLSPZuLJ0R90Zaa6tj+awX9NDO2DPzjxEEJuY0CFV+g@mail.gmail.com \
    --to=mad@cs.technion.ac.il \
    --cc=berberic@fmi.uni-passau.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nadav.amit@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox