linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Anders Grafström" <grfstrm@users.sourceforge.net>
To: Daniel Mack <daniel@caiaq.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	AKML <linux-arm-kernel@lists.infradead.org>,
	linux-wireless@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Sven Neumann <s.neumann@raumfeld.com>,
	stable@kernel.org
Subject: Re: Memory corruption with 2.6.32.10, but not with 2.6.34-rc3
Date: Thu, 01 Apr 2010 19:29:59 +0200	[thread overview]
Message-ID: <4BB4D817.1050603@users.sourceforge.net> (raw)
In-Reply-To: <20100401132156.GJ30807@buzzloop.caiaq.de>

Daniel Mack wrote:
> We would like to have a fix for this annoying bug in the stable series
> (especially 2.6.32.x) as well, but I don't have much ideas about where
> to search for it. Hence, I would appreciate if maintainers could think
> about any possible commits in the described time window which haven't
> reached stable. Does the description ring anyone's bell?
> 
> I can cherry-pick things if anyone pin-points something and run
> lont-time tests again. Any pointer appreciated.

You could try this one:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8e4971f2fb2380ce66196136e113d04196b80fcd


  parent reply	other threads:[~2010-04-01 17:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 13:21 Memory corruption with 2.6.32.10, but not with 2.6.34-rc3 Daniel Mack
2010-04-01 16:50 ` Greg KH
2010-04-01 17:00   ` Daniel Mack
2010-04-01 16:51 ` Greg KH
2010-04-01 16:58   ` Daniel Mack
2010-04-05 10:59     ` Uwe Kleine-König
2010-04-01 17:29 ` Anders Grafström [this message]
2010-04-01 17:57   ` Daniel Mack

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=4BB4D817.1050603@users.sourceforge.net \
    --to=grfstrm@users.sourceforge.net \
    --cc=daniel@caiaq.de \
    --cc=gregkh@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.neumann@raumfeld.com \
    --cc=stable@kernel.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;
as well as URLs for NNTP newsgroup(s).