From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752599AbcFFFcX (ORCPT ); Mon, 6 Jun 2016 01:32:23 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:5167 "EHLO mx0b-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751568AbcFFFcW (ORCPT ); Mon, 6 Jun 2016 01:32:22 -0400 X-IBM-Helo: d23dlp02.au.ibm.com X-IBM-MailFrom: xinhui.pan@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Mon, 06 Jun 2016 13:31:30 +0800 From: xinhui User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Michael Ellerman , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org CC: Andrzej Hajda , Christophe Jaillet , Hari Bathini , Paul Mackerras , tglx@linutronix.de, Nathan Fontenot Subject: Re: powerpc/nvram: Fix an incorrect partition merge References: <3rLj4P6Swcz9t6B@ozlabs.org> In-Reply-To: <3rLj4P6Swcz9t6B@ozlabs.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16060605-0040-0000-0000-000001AE7483 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16060605-0041-0000-0000-000009D045CC Message-Id: <57550AB2.8090500@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-06-06_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1606060068 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016年06月03日 19:47, Michael Ellerman wrote: > On Thu, 2015-10-12 at 07:30:02 UTC, xinhui wrote: >> From: Pan Xinhui >> >> When we merge two contiguous partitions whose signatures are marked >> NVRAM_SIG_FREE, We need update prev's length and checksum, then write it >> to nvram, not cur's. So lets fix this mistake now. >> >> Also use memset instead of strncpy to set the partition's name. It's >> more readable if we want to fill up with duplicate chars . > > Does this ever happen in practice? ie. should we backport the fix to stable > kernels? > I did not see that nvram warning in practice. BUT I suggest to backport it to stable kernel. :) Let me recall the story. :) In past days, I was using pstore to keep some kernel logs. and sometimes I found my own logs and the panic logs did not show. pstore use a fixed-address reserved memory In x86 while nvram instead in ppc. Then I spent some days to review the nvram codes. And worked out three patches to fix all issues that I found in nvram. BUT looks like I only sent out two of them. :) I lost the third patch maybe... > Has it always been broken? > no. after nvram partition corruption hit, all nvram partitions will be erased and re-alloc after the second machine reboot. I don't know who does it but i guess it is the firmware. :) thanks xinhui > cheers >