Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp443638imu; Fri, 4 Jan 2019 00:19:02 -0800 (PST) X-Google-Smtp-Source: ALg8bN5W66SxqK4ivbCkt5xsHACrJ95ZqaRpZMB2H7tZQocfuMfTye4Nr04DlqrwRta6FX5lApTQ X-Received: by 2002:a63:a611:: with SMTP id t17mr19553035pge.338.1546589942670; Fri, 04 Jan 2019 00:19:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546589942; cv=none; d=google.com; s=arc-20160816; b=Z+94zSudwxmm4Fiy2XE8tvEEO5jpFdvZyz7NQJ0w/29JyVEK6x2EEsxFfcGaTZoyT3 KfdaPvHwzlLTiolhYO/7427w6HE1AjbY31M26R9q6Vuaslej/EW30/lHmj+Xe+OmIM1h soVR8g4uUndWVaDOS10WPDNIEEwBbky1FUilrWBi1U/jHUNmye4g9+VfqQJunyf7Oc5f Rb+Q4YtJdxNPNV1qmnhYFfB6bVAhvBFEMEZRmTfs8Flz7smk8peQHHaDyMHmg9qpPeun A87bfLuP69uteMEF60h+kLVu8ArRFW3kkG0dVVU3gnt+S+WazXmVw7AxNoxFMKzoKG7G 7ZpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=oeAknq6bsd8Qif9bshyXXLkWP+XbcB0rqgkLZ/LBO78=; b=M//logm4NqQdhyuPw2EPWB0Yl8gu9i01A5JyWdbqL+VlZpAL3pmVYfLS+nN6gdWaTm OTV4ZqVUoTqdSI2elVh28+GWdFmocoK6V/mbt+y+P1WwplRcgpQ1tmpfPGFKLqFZYkBB d6MwhlWax6Q0SrjBd8Z5m9KZRZ8xMQy1uoJ7TdNIiMReQwjEnHg5ne5mgi9ASMSRApU9 GUJStcW4HOTeLsLlAE8QFlch+eltgXRfIWUxmuN4WknFchMotGNDKwfXX8X+FopfgN/S 8FU2XP34gM1LgavQ3QeDYVQf8+Gxu6CTEoHdhNLb/NCuaCTM1gwPMyZ2kicGJFQwhdjt KzJA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m35si41315867pgb.246.2019.01.04.00.18.47; Fri, 04 Jan 2019 00:19:02 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726647AbfADHDi (ORCPT + 99 others); Fri, 4 Jan 2019 02:03:38 -0500 Received: from smtp2207-205.mail.aliyun.com ([121.197.207.205]:37216 "EHLO smtp2207-205.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725913AbfADHDh (ORCPT ); Fri, 4 Jan 2019 02:03:37 -0500 X-Alimail-AntiSpam: AC=CONTINUE;BC=0.07863735|-1;CH=green;FP=0|0|0|0|0|-1|-1|-1;HT=e01l07383;MF=liaoweixiong@allwinnertech.com;NM=1;PH=DS;RN=5;RT=5;SR=0;TI=SMTPD_---.DhF606j_1546585413; Received: from 172.16.10.102(mailfrom:liaoweixiong@allwinnertech.com fp:SMTPD_---.DhF606j_1546585413) by smtp.aliyun-inc.com(10.147.42.135); Fri, 04 Jan 2019 15:03:33 +0800 Subject: Re: [RFC v4 0/3] pstore/rom: new support logger for block devices To: "Luck, Tony" , Kees Cook , Anton Vorontsov , Colin Cross Cc: "linux-kernel@vger.kernel.org" References: <1546501533-1855-1-git-send-email-liaoweixiong@allwinnertech.com> <3908561D78D1C84285E8C5FCA982C28F7D4B623C@ORSMSX110.amr.corp.intel.com> From: =?UTF-8?B?5buW5aiB6ZuE?= Message-ID: Date: Fri, 4 Jan 2019 15:03:41 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F7D4B623C@ORSMSX110.amr.corp.intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org hi Tony: On 2019-01-04 01:18, Luck, Tony wrote: > I'm curious why you call this "pstore/rom" rather than the more descriptive "pstore/block". Because there is "pstore/ram", so i name it as "pstore/rom". It's nice to rename it "pstore/block", i will change it in next version of patch. > > It looks to be a really good idea. Should i add "Acked-by" in next version of patch? I have little experience in sending patch to upstream linux. > > I think you need to document how the "write" function for the block device must be written. > Since pstore calls this at "panic" time, the write path: > > + Cannot allocate any memory > + Must be polled, not interrupt driven > + Cannot take any locks that may be held by regular code > + ... perhaps other restrictions that I can't think of right now > > The memory allocation restriction is likely easy to get around. Just allocate anything > you need at pstore "init" time rather than waiting until the panic. >I will provide a documemt for it in next version of patch. > -Tony >