All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ondrej Zary <linux@rainbow-software.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Balbir Singh <balbir@in.ibm.com>, Hugh Dickins <hughd@google.com>
Subject: Re: 2.6.35.5: hibernation broken... AGAIN
Date: Wed, 17 Nov 2010 22:12:01 +0100	[thread overview]
Message-ID: <201011172212.01433.rjw@sisk.pl> (raw)
In-Reply-To: <20101117130422.d9de48d8.akpm@linux-foundation.org>

On Wednesday, November 17, 2010, Andrew Morton wrote:
> On Wed, 17 Nov 2010 21:53:52 +0100
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > On Wednesday, November 17, 2010, Ondrej Zary wrote:
> > > Hello,
> > > the nasty memory-corrupting hibernation bug 
> > > https://bugzilla.kernel.org/show_bug.cgi?id=15753 is back since 2.6.35.5.
> > > 2.6.35.4 works fine, 2.6.35.5 crashes after two days.
> > > 
> > > It seems to be caused by b77c254d8d66e5e9aa81239fedba9f3d568097d9.
> > 
> > Can you, _please_, always put all of the basic commit info (subject, author,
> > who signed it off) in bug reports?
> > 
> > In this particular case I don't have a -stable tree handy at the moment and
> > can't even see what the commit is.
> 
> You can simply do a google search for the commit ID.  It is

Thanks! :-)

> commit b77c254d8d66e5e9aa81239fedba9f3d568097d9
> Author: Hugh Dickins <hughd@google.com>
> Date:   Thu Sep 9 16:38:09 2010 -0700
> 
>     swap: prevent reuse during hibernation

So I guess we should Cc Hugh ...

  reply	other threads:[~2010-11-17 21:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 10:39 2.6.35.5: hibernation broken... AGAIN Ondrej Zary
2010-11-17 20:53 ` Rafael J. Wysocki
2010-11-17 21:04   ` Andrew Morton
2010-11-17 21:12     ` Rafael J. Wysocki [this message]
2010-11-17 21:18       ` Ondrej Zary
2010-11-17 23:46         ` Hugh Dickins
2010-11-20 15:07           ` Ondrej Zary
2010-11-26 11:43           ` Ondrej Zary
2010-11-26 23:10             ` Rafael J. Wysocki
2010-11-27 14:58               ` Ondrej Zary
2010-11-27 20:47                 ` Rafael J. Wysocki
2010-11-30 22:16                   ` Hugh Dickins
2010-11-30 23:07                     ` Rafael J. Wysocki
2010-12-01  0:38                       ` Rafael J. Wysocki
2010-12-01  0:53                         ` KAMEZAWA Hiroyuki
2010-12-01 21:25                           ` Rafael J. Wysocki
2010-12-01 22:23                             ` Rafael J. Wysocki
2010-12-01 23:37                               ` KAMEZAWA Hiroyuki
2010-12-02  0:00                                 ` Rafael J. Wysocki
2010-12-01  1:21                         ` Hugh Dickins
2010-12-01 20:57                           ` Rafael J. Wysocki
2010-12-06 21:09                   ` Ondrej Zary
2010-12-06 22:57                     ` Rafael J. Wysocki
2010-11-26 20:24           ` Rafael J. Wysocki

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=201011172212.01433.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@in.ibm.com \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.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 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.