linux-kernel - Re: [PATCH] sp5100_tco: Remove code that may cause a boot failure

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] [day] [month] [year] [list]

Date:	Tue, 26 Feb 2013 00:04:18 +0900
From:	Tanaka Takahisa <mc74hc00@...il.com>
To:	Paul Menzel <paulepanter@...rs.sourceforge.net>
Cc:	linux-watchdog@...r.kernel.org, Wim Van Sebroeck <wim@...ana.be>,
	Arkadiusz Miskiewicz <arekm@...en.pl>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jonathan Nieder <jrnieder@...il.com>,
	linux-kernel@...r.kernel.org,
	Florian Mickler <florian@...kler.org>,
	Joseph Salisbury <joseph.salisbury@...onical.com>,
	Joseph Salisbury <josephtsalisbury@...il.com>
Subject: Re: [PATCH] sp5100_tco: Remove code that may cause a boot failure

Hi Paul,

Thank you for always helping!

2013/2/24 Paul Menzel <paulepanter@...rs.sourceforge.net>:
> Dear Takahisa,
>

> all SB700 boards or just a specific one?

The problem is found only on the ASUSTeK M3A78-CM at the moment. The
problem prevents OS from booting, and, It's critical. Therefor, I
thought that It is safe to delete the reprogramming code of chipset
until a reason is found.

https://lkml.org/lkml/2013/2/23/10


> Is that problem there since the first implementation or just with your
> second patch? (I do not have the commit hashes and summaries ready.)

The problem occurred in both the first implementation and my second patch.
Please refer to following LKML thread.

https://lkml.org/lkml/2013/2/14/271


> The Bugzilla entry is not really related to this report. Please make
> clear that this is the report the original patch wanted to fix. As
> nobody closed it yet, it does not need to be reopened.

Sorry, you just said it. I will replace the URL of Bugzilla with URL
of LKML thread, and resend the
patch to LKML.


> To address Greg’s comment, your patch first has to land in Linus’ master
> branch and only then it can be backported/applied to the stable series.
> This will be done automatically if you just add

It's my mistake that I add stable@...r.kernel.org to CC. This patch
isn't able to apply Linus master branch, because this patch is
dependent on second patch which isn't merged into Linus' master
branch.


Regards,
Takahisa
--
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/