From patchwork Thu Aug 16 14:52:03 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Richard Genoud X-Patchwork-Id: 178022 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from merlin.infradead.org (merlin.infradead.org [IPv6:2001:4978:20e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id C22C82C0079 for ; Fri, 17 Aug 2012 00:54:01 +1000 (EST) Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1T21RH-0003XF-HZ; Thu, 16 Aug 2012 14:52:47 +0000 Received: from mail-wg0-f49.google.com ([74.125.82.49]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1T21RC-0003W3-1a for linux-mtd@lists.infradead.org; Thu, 16 Aug 2012 14:52:43 +0000 Received: by wgbez12 with SMTP id ez12so1796264wgb.18 for ; Thu, 16 Aug 2012 07:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:x-mailer:in-reply-to:references; bh=72JYPoeE8mDLfePOaieK3CMQvpeWTeYf7dP7wBZ/Vqw=; b=Zof1qm/V/wBJUzAfKyXhke9Clgaff6i08InaCUkMupGn7O+jK6HJGkzys+dydd0Bmj mJA7xYdXB/HMFmmbhjWiwcv4fG1jJiOC9+8grRXV0dtyYgBSxg4Rl9FDLUpDE88ATnD9 I1mvpFMHY36E/Dqg2n+91wppUiHVm0zaVdfAOqQWhIJgdAGYHiUrjGzSZkTSWGiPYgk2 KZPa60JGmXvwOJkCDynbYMS6LDEyhyQwX7H/hQ1ga4IsCzimxy3o2oB7EBUsgDdU5gDi OxfIR6HmjAte+0VR1LqNBqQ4/eldpN7dReyUFzxXwcogsiyfWd41pmgvoiCFjJBqR3MO g+pg== Received: by 10.180.97.106 with SMTP id dz10mr3771355wib.21.1345128760303; Thu, 16 Aug 2012 07:52:40 -0700 (PDT) Received: from localhost.localdomain (lyon.paratronic.fr. [213.41.177.106]) by mx.google.com with ESMTPS id z11sm6308895wiv.10.2012.08.16.07.52.38 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 16 Aug 2012 07:52:39 -0700 (PDT) From: Richard Genoud To: Artem Bityutskiy Subject: [PATCH 2/2] UBI: add ioctl for max_beb_per1024 Date: Thu, 16 Aug 2012 16:52:03 +0200 Message-Id: <1345128723-13582-3-git-send-email-richard.genoud@gmail.com> X-Mailer: git-send-email 1.7.2.5 In-Reply-To: <1345042639.3393.150.camel@sauron.fi.intel.com> References: <1345042639.3393.150.camel@sauron.fi.intel.com> X-Spam-Note: CRM114 invocation failed X-Spam-Score: -2.7 (--) X-Spam-Report: SpamAssassin version 3.3.2 on merlin.infradead.org summary: Content analysis details: (-2.7 points) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [74.125.82.49 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (richard.genoud[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Cc: Richard Genoud , David Woodhouse , linux-mtd@lists.infradead.org, Shmulik Ladkani , linux-kernel@vger.kernel.org X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Sender: linux-mtd-bounces@lists.infradead.org Errors-To: linux-mtd-bounces+incoming=patchwork.ozlabs.org@lists.infradead.org This patch provides the possibility to adjust the "maximum expected number of bad blocks per 1024 blocks" (max_beb_per1024) for each mtd device from UBI_IOCATT ioctl. The majority of NAND devices have their max_beb_per1024 equal to 20, but sometimes it's more. We already could adjust that via a kernel parameter, now we can also use UBI_IOCATT ioctl: struct ubi_attach_req { __s32 ubi_num; __s32 mtd_num; __s32 vid_hdr_offset; __u8 max_beb_per1024; __s8 padding[11]; }; Signed-off-by: Richard Genoud --- drivers/mtd/ubi/cdev.c | 9 ++++++++- include/mtd/ubi-user.h | 19 ++++++++++++++++++- 2 files changed, 26 insertions(+), 2 deletions(-) diff --git a/drivers/mtd/ubi/cdev.c b/drivers/mtd/ubi/cdev.c index e0027e7..d268b42 100644 --- a/drivers/mtd/ubi/cdev.c +++ b/drivers/mtd/ubi/cdev.c @@ -1006,12 +1006,19 @@ static long ctrl_cdev_ioctl(struct file *file, unsigned int cmd, } /* + * For compatibility with older user-space tools, + * a zero value should be treated like a default value + */ + if (!req.max_beb_per1024) + req.max_beb_per1024 = MTD_UBI_DEFAULT_BEB_LIMIT; + + /* * Note, further request verification is done by * 'ubi_attach_mtd_dev()'. */ mutex_lock(&ubi_devices_mutex); err = ubi_attach_mtd_dev(mtd, req.ubi_num, req.vid_hdr_offset, - MTD_UBI_DEFAULT_BEB_LIMIT); + req.max_beb_per1024); mutex_unlock(&ubi_devices_mutex); if (err < 0) put_mtd_device(mtd); diff --git a/include/mtd/ubi-user.h b/include/mtd/ubi-user.h index 8787349..77cd0d1 100644 --- a/include/mtd/ubi-user.h +++ b/include/mtd/ubi-user.h @@ -222,6 +222,7 @@ enum { * @ubi_num: UBI device number to create * @mtd_num: MTD device number to attach * @vid_hdr_offset: VID header offset (use defaults if %0) + * @max_beb_per1024: Maximum expected bad eraseblocks per 1024 eraseblocks * @padding: reserved for future, not used, has to be zeroed * * This data structure is used to specify MTD device UBI has to attach and the @@ -245,12 +246,28 @@ enum { * be 2KiB-64 bytes = 1984. Note, that this position is not even 512-bytes * aligned, which is OK, as UBI is clever enough to realize this is 4th * sub-page of the first page and add needed padding. + * + * The @max_beb_per1024 is the maximum bad eraseblocks UBI expects on the ubi + * device per 1024 eraseblocks. + * This value is often given in an other form in the NAND datasheet (min NVB + * i.e. minimal number of valid blocks). The maximum expected bad eraseblocks + * per 1024 is then: + * 1024 * (1 - MinNVB / MaxNVB) + * Which gives 20 for most NAND devices. + * This limit is used in order to derive amount of eraseblock UBI reserves for + * handling new bad blocks. + * If the device has more bad eraseblocks than this limit, UBI does not reserve + * any physical eraseblocks for new bad eraseblocks, but attempts to use + * available eraseblocks (if any). + * The accepted range is 0-255. If 0 is given, the default value + * MTD_UBI_DEFAULT_BEB_LIMIT will be used for compatibility. */ struct ubi_attach_req { __s32 ubi_num; __s32 mtd_num; __s32 vid_hdr_offset; - __s8 padding[12]; + __u8 max_beb_per1024; + __s8 padding[11]; }; /**