linux-kernel - Re: [PATCH 1/3] agp/intel: remove restore in resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090910182257.91c66541.akpm@linux-foundation.org>
Date:	Thu, 10 Sep 2009 18:22:57 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Zhenyu Wang <zhenyuw@...ux.intel.com>
Cc:	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	stable@...nel.org, stern@...land.harvard.edu
Subject: Re: [PATCH 1/3] agp/intel: remove restore in resume

On Fri, 11 Sep 2009 09:03:42 +0800 Zhenyu Wang <zhenyuw@...ux.intel.com> wrote:

> On 2009.09.10 13:42:52 -0700, Andrew Morton wrote:
> > On Fri,  4 Sep 2009 09:43:34 +0800
> > Zhenyu Wang <zhenyuw@...ux.intel.com> wrote:
> > 
> > > As early pci resume has already restored config for host
> > > bridge and graphics device, don't need to restore it again,
> > > which might cause problem on some chips, like 845G tested by
> > > Alan Stern.
> > > 
> > > Cc: Stable Team <stable@...nel.org>
> > > Cc: Alan Stern <stern@...land.harvard.edu>
> > > Signed-off-by: Zhenyu Wang <zhenyuw@...ux.intel.com>
> > 
> > Why were these patches cc'ed to stable@...nel.org?  There's nothing in
> > the changelog which explains why the problem which is being fixed is
> > sufficiently serious to warrant backporting the patch.
> 
> Sorry, Andrew. I wasn't awared that an earlier version of this patch
> has already been merged, and this patch fixed resume issue on Alan's
> 845G, which was discussed on linux-pm list, I should have made more
> clear note about that. We've also seen other resume failure bugs, which
> might be relate to this one. So I think it should be fine for stable.

We still don't have a changelog for this patch which explains to the
-stable maintainers (and those who follow -stable commits):

a) what bug this patch fixes and

b) why they should merge it - this should be ovbious if a) is provided.

this isn't pointless paperwork - it matters to those who maintain and
use the -stable tree.  Vague references to traffic on the linux-pm list
aren't at all useful.

>From my reading of the above, it appears that Alan was experiencing
<secretbug> and this patch was tested and fixed it, yes?

> > 
> > Was there a [patch 3/3]?  I didn't receive it.
> 
> sorry, my mistake, the 3/3 commit on my tree is not ready to send, 
> forget to make git format-patch happy.

OK.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/