All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table
@ 2018-07-20 12:30 David Owens
  2018-07-20 12:40 ` Matthew Weber
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: David Owens @ 2018-07-20 12:30 UTC (permalink / raw)
  To: buildroot

A regression in the mtd package prevents non-consecutive ubi volume IDs
from working properly.  This change reverts the commit [0].  The issue
was originally described on the mtd mailing list:

http://lists.infradead.org/pipermail/linux-mtd/2018-June/081562.html

[0] http://git.infradead.org/mtd-utils.git/commitdiff/dede98ffb706676309488d7cc660f569548d5930

Signed-off-by: David Owens <david.owens@rockwellcollins.com>
---
 ...correct-error-number-in-ubi_get_vol_info1.patch | 91 ++++++++++++++++++++++
 1 file changed, 91 insertions(+)
 create mode 100644 package/mtd/0001-revert-return-correct-error-number-in-ubi_get_vol_info1.patch

diff --git a/package/mtd/0001-revert-return-correct-error-number-in-ubi_get_vol_info1.patch b/package/mtd/0001-revert-return-correct-error-number-in-ubi_get_vol_info1.patch
new file mode 100644
index 0000000..aaed353
--- /dev/null
+++ b/package/mtd/0001-revert-return-correct-error-number-in-ubi_get_vol_info1.patch
@@ -0,0 +1,91 @@
+From 0f833ac73ad631248826386e2918d8571ecf0347 Mon Sep 17 00:00:00 2001
+From: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
+Date: Sat, 9 Jun 2018 16:45:22 +0200
+Subject: [PATCH] Revert "Return correct error number in ubi_get_vol_info1"
+
+This reverts commit dede98ffb706676309488d7cc660f569548d5930.
+
+The original commit tried to fix a descrepancy between the implementation
+and the documentation by making the implementation comply.
+
+When making the change, it was overlooked, that ubinfo and ubirename were
+written against the implementation instead of the behaviour specified by
+the documentation. So were further internal functions like
+ubi_get_vol_info1_nm which further breaks ubirmvol.
+
+A report with an outline of a resulting problem can be read on
+the mailing list:
+
+http://lists.infradead.org/pipermail/linux-mtd/2018-June/081562.html
+
+From the report:
+
+steps to reproduce: have mtd-utils 2.0.1 or 2.0.2
+
+0. make a bunch of ubi volumes in sequential order
+
+ubimkvol /dev/ubi0 -s 64KiB -N test1
+ubimkvol /dev/ubi0 -s 64KiB -N test2
+ubimkvol /dev/ubi0 -s 64KiB -N test3
+ubimkvol /dev/ubi0 -s 64KiB -N test4
+..
+
+1. delete the test1 volume, making a hole in the volume table
+
+ubirmvol /dev/ubi0 -N test1
+
+2. try an affected tool (i.e. "ubirmvol /dev/ubi0 -N test4" )
+
+ |root at mr24:/# ubirmvol /dev/ubi0 -N test4
+ |ubirmvol: error!: cannot find UBI volume "test4"
+ |         error 19 (No such device)
+
+or "ubinfo -a"
+
+ | root at mr24:/# ubinfo -a
+ | UBI version:                    1
+ | Count of UBI devices:           1
+ | UBI control device major/minor: 10:59
+ | Present UBI devices:            ubi0
+ |
+ | ubi0
+ | Volumes count:                           11
+ | Logical eraseblock size:                 15872 bytes, 15.5 KiB
+ | Total amount of logical eraseblocks:     1952 (30982144 bytes, 29.5 MiB)
+ | Amount of available logical eraseblocks: 75 (1190400 bytes, 1.1 MiB)
+ | Maximum count of volumes                 92
+ | Count of bad physical eraseblocks:       0
+ | Count of reserved physical eraseblocks:  40
+ | Current maximum erase counter value:     984
+ | Minimum input/output unit size:          512 bytes
+ | Character device major/minor:            251:0
+ | ubinfo: error!: libubi failed to probe volume 5 on ubi0
+ |        error 19 (No such device)
+ | Present volumes:                         0, 1, 2, 3, 4root at mr24:/#
+
+Reported-by: Christian Lamparter <chunkeey@gmail.com>
+Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
+---
+ lib/libubi.c | 5 +----
+ 1 file changed, 1 insertion(+), 4 deletions(-)
+
+diff --git a/lib/libubi.c b/lib/libubi.c
+index b50e68a..978b433 100644
+--- a/lib/libubi.c
++++ b/lib/libubi.c
+@@ -1240,11 +1240,8 @@ int ubi_get_vol_info1(libubi_t desc, int dev_num, int vol_id,
+ 	info->dev_num = dev_num;
+ 	info->vol_id = vol_id;
+ 
+-	if (vol_get_major(lib, dev_num, vol_id, &info->major, &info->minor)) {
+-		if (errno == ENOENT)
+-			errno = ENODEV;
++	if (vol_get_major(lib, dev_num, vol_id, &info->major, &info->minor))
+ 		return -1;
+-	}
+ 
+ 	ret = vol_read_data(lib->vol_type, dev_num, vol_id, buf, 50);
+ 	if (ret < 0)
+-- 
+2.14.4
+
-- 
1.9.1

^ permalink raw reply related	[flat|nested] 6+ messages in thread

* [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table
  2018-07-20 12:30 [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table David Owens
@ 2018-07-20 12:40 ` Matthew Weber
  2018-07-20 13:47   ` David Owens
  2018-08-10 14:25 ` Thomas Petazzoni
  2018-08-24  8:07 ` Peter Korsgaard
  2 siblings, 1 reply; 6+ messages in thread
From: Matthew Weber @ 2018-07-20 12:40 UTC (permalink / raw)
  To: buildroot

David,

On Fri, Jul 20, 2018 at 7:30 AM, David Owens
<david.owens@rockwellcollins.com> wrote:
> A regression in the mtd package prevents non-consecutive ubi volume IDs
> from working properly.  This change reverts the commit [0].  The issue
> was originally described on the mtd mailing list:
>
> http://lists.infradead.org/pipermail/linux-mtd/2018-June/081562.html
>
> [0] http://git.infradead.org/mtd-utils.git/commitdiff/dede98ffb706676309488d7cc660f569548d5930
>

Are you thinking this patch would be for the LTS and then separately a
patchset to bump the MTD version would be better for master?

Matt

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table
  2018-07-20 12:40 ` Matthew Weber
@ 2018-07-20 13:47   ` David Owens
  2018-07-25 21:30     ` Matthew Weber
  0 siblings, 1 reply; 6+ messages in thread
From: David Owens @ 2018-07-20 13:47 UTC (permalink / raw)
  To: buildroot

On Fri, Jul 20, 2018 at 7:40 AM, Matthew Weber <
matthew.weber@rockwellcollins.com> wrote:

> David,
>
> On Fri, Jul 20, 2018 at 7:30 AM, David Owens
> <david.owens@rockwellcollins.com> wrote:
> > A regression in the mtd package prevents non-consecutive ubi volume IDs
> > from working properly.  This change reverts the commit [0].  The issue
> > was originally described on the mtd mailing list:
> >
> > http://lists.infradead.org/pipermail/linux-mtd/2018-June/081562.html
> >
> > [0] http://git.infradead.org/mtd-utils.git/commitdiff/
> dede98ffb706676309488d7cc660f569548d5930
> >
>
> Are you thinking this patch would be for the LTS and then separately a
> patchset to bump the MTD version would be better for master?
>
> Matt
>

I think the patch should be applied to LTS at a minimum but it also might
make
sense to apply to master.  The latest MTD version (2.0.2) has the same
problem
so simply bumping the MTD versions won't help until a new release is
available.

-Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180720/36b3910c/attachment.html>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table
  2018-07-20 13:47   ` David Owens
@ 2018-07-25 21:30     ` Matthew Weber
  0 siblings, 0 replies; 6+ messages in thread
From: Matthew Weber @ 2018-07-25 21:30 UTC (permalink / raw)
  To: buildroot

David,

On Fri, Jul 20, 2018 at 8:47 AM, David Owens
<david.owens@rockwellcollins.com> wrote:
> On Fri, Jul 20, 2018 at 7:40 AM, Matthew Weber
> <matthew.weber@rockwellcollins.com> wrote:
>>
>> David,
>>
>> On Fri, Jul 20, 2018 at 7:30 AM, David Owens
>> <david.owens@rockwellcollins.com> wrote:
>> > A regression in the mtd package prevents non-consecutive ubi volume IDs
>> > from working properly.  This change reverts the commit [0].  The issue
>> > was originally described on the mtd mailing list:
>> >
>> > http://lists.infradead.org/pipermail/linux-mtd/2018-June/081562.html
>> >
>> > [0]
>> > http://git.infradead.org/mtd-utils.git/commitdiff/dede98ffb706676309488d7cc660f569548d5930
>> >
>>
>> Are you thinking this patch would be for the LTS and then separately a
>> patchset to bump the MTD version would be better for master?
>>
>> Matt
>
>
> I think the patch should be applied to LTS at a minimum but it also might
> make
> sense to apply to master.  The latest MTD version (2.0.2) has the same
> problem
> so simply bumping the MTD versions won't help until a new release is
> available.
>

Ok, yeah then both LTS and master. (btw, please use plain text email)

Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table
  2018-07-20 12:30 [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table David Owens
  2018-07-20 12:40 ` Matthew Weber
@ 2018-08-10 14:25 ` Thomas Petazzoni
  2018-08-24  8:07 ` Peter Korsgaard
  2 siblings, 0 replies; 6+ messages in thread
From: Thomas Petazzoni @ 2018-08-10 14:25 UTC (permalink / raw)
  To: buildroot

Hello,

On Fri, 20 Jul 2018 07:30:07 -0500, David Owens wrote:
> A regression in the mtd package prevents non-consecutive ubi volume IDs
> from working properly.  This change reverts the commit [0].  The issue
> was originally described on the mtd mailing list:
> 
> http://lists.infradead.org/pipermail/linux-mtd/2018-June/081562.html
> 
> [0] http://git.infradead.org/mtd-utils.git/commitdiff/dede98ffb706676309488d7cc660f569548d5930
> 
> Signed-off-by: David Owens <david.owens@rockwellcollins.com>
> ---
>  ...correct-error-number-in-ubi_get_vol_info1.patch | 91 ++++++++++++++++++++++
>  1 file changed, 91 insertions(+)
>  create mode 100644 package/mtd/0001-revert-return-correct-error-number-in-ubi_get_vol_info1.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table
  2018-07-20 12:30 [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table David Owens
  2018-07-20 12:40 ` Matthew Weber
  2018-08-10 14:25 ` Thomas Petazzoni
@ 2018-08-24  8:07 ` Peter Korsgaard
  2 siblings, 0 replies; 6+ messages in thread
From: Peter Korsgaard @ 2018-08-24  8:07 UTC (permalink / raw)
  To: buildroot

>>>>> "David" == David Owens <david.owens@rockwellcollins.com> writes:

 > A regression in the mtd package prevents non-consecutive ubi volume IDs
 > from working properly.  This change reverts the commit [0].  The issue
 > was originally described on the mtd mailing list:

 > http://lists.infradead.org/pipermail/linux-mtd/2018-June/081562.html

 > [0] http://git.infradead.org/mtd-utils.git/commitdiff/dede98ffb706676309488d7cc660f569548d5930

 > Signed-off-by: David Owens <david.owens@rockwellcollins.com>

Committed to 2018.02.x and 2018.05.x, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2018-08-24  8:07 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-07-20 12:30 [Buildroot] [PATCH 1/1] mtd: Allow holes in volume ID table David Owens
2018-07-20 12:40 ` Matthew Weber
2018-07-20 13:47   ` David Owens
2018-07-25 21:30     ` Matthew Weber
2018-08-10 14:25 ` Thomas Petazzoni
2018-08-24  8:07 ` Peter Korsgaard

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.