public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tim Sander <tim@krieglstein.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 3.4.28-rt40 tglx fix imx.c spinlock
Date: Thu, 14 Feb 2013 23:35:03 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1302142334120.22263@ionos> (raw)
In-Reply-To: <16398840.IK9i4U2q2d@dabox>

On Thu, 14 Feb 2013, Tim Sander wrote:
> > That's true, but w/o seing the OOM output I can't tell what's
> > exhausting the memory.
> When fuzzing the serial port one probably should switch of sysreq. It seems 
> as if there is a break send somehow and then it selects the OOM option.
> So when switching of MAGIC_SYSRQ the OOMs are gone. So its a non issue.

Amazing that you get the break+oom combo out of that fuzzer!

  reply	other threads:[~2013-02-14 22:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 16:10 3.4.28-rt40 arm freescale imx35 pcm43 Tim Sander
2013-02-06 16:43 ` Tim Sander
2013-02-07  8:57   ` 3.4.28-rt40 arm freescale imx35 pcm43 - patch 86236252d2449313bdbac790023cbc957bf6e426 is cause Tim Sander
2013-02-13 12:13     ` Thomas Gleixner
2013-02-13 17:07       ` Tim Sander
2013-02-13 17:25         ` Thomas Gleixner
2013-02-13 17:40         ` Thomas Gleixner
2013-02-14 15:38           ` [PATCH] 3.4.28-rt40 tglx fix imx.c spinlock Tim Sander
2013-02-14 22:35             ` Thomas Gleixner [this message]
2013-02-15  1:13               ` Paul Gortmaker
2013-02-15  7:05                 ` [PATHC] 3.6 spinlock fix Tim Sander
2013-02-15 10:18                   ` Thomas Gleixner
2013-02-13 11:59   ` 3.4.28-rt40 arm freescale imx35 pcm43 Thomas Gleixner

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=alpine.LFD.2.02.1302142334120.22263@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tim@krieglstein.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