public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Wurm, Stephan" <Stephan.Wurm@a-eberle.de>
To: Richard Weinberger <richard@nod.at>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Eigner, Johannes" <Johannes.Eigner@a-eberle.de>
Subject: Re: ubiblock: null pointer dereference using scatterlist in work_queue
Date: Fri, 21 Jul 2023 07:41:36 +0000	[thread overview]
Message-ID: <ZLo2rpBa+MiHaIR1@PC-LX-Wurm> (raw)
In-Reply-To: <ZLf1dqe1DUhfXQ4R@PC-LX-Wurm>

Am 19.07.2023 um 16:38 hat Stephan Wurm geschrieben:
> Am 19.07.2023 um 16:31 hat Richard Weinberger geschrieben:
> > ----- Ursprüngliche Mail -----
> > > Von: "Stephan Wurm" <stephan.wurm@a-eberle.de>
> > >> > We did not check other stacked devices, but we'll give this a try.
> >
> > Did you find the time to check with dmcrypt?
> Unfortunately not. I am still preparing this and I do not have access on
> the hardware until Friday.
Today I was able to build the system with dm-crypt (using LUKS2 and
PBKDF2) and successfully boot from sdcard.

But when booting from the ubiblock device, I get the same null pointer
dereference as for dm-verity.

This really seems to be related to devicemapper interfering with the
ubiblock device.


To add some more details on the setup, here is the output of ubinfo:

# ubinfo -a
UBI version:                    1
Count of UBI devices:           1
UBI control device major/minor: 10:125
Present UBI devices:            ubi0

ubi0
Volumes count:                           5
Logical eraseblock size:                 253952 bytes, 248.0 KiB
Total amount of logical eraseblocks:     4092 (1039171584 bytes, 991.0
MiB)
Amount of available logical eraseblocks: 177 (44949504 bytes, 42.8 MiB)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       4
Count of reserved physical eraseblocks:  76
Current maximum erase counter value:     56
Minimum input/output unit size:          4096 bytes
Character device major/minor:            242:0
Present volumes:                         0, 1, 2, 3, 4

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        248 LEBs (62980096 bytes, 60.0 MiB)
State:       OK
Name:        fit0
Character device major/minor: 242:1
-----------------------------------
Volume ID:   1 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        248 LEBs (62980096 bytes, 60.0 MiB)
State:       OK
Name:        fit1
Character device major/minor: 242:2
-----------------------------------
Volume ID:   2 (on ubi0)
Type:        static
Alignment:   1
Size:        1404 LEBs (356548608 bytes, 340.0 MiB)
Data bytes:  137355264 bytes (130.9 MiB)
State:       OK
Name:        root0
Character device major/minor: 242:3
-----------------------------------
Volume ID:   3 (on ubi0)
Type:        static
Alignment:   1
Size:        1404 LEBs (356548608 bytes, 340.0 MiB)
Data bytes:  168460288 bytes (160.6 MiB)
State:       OK
Name:        root1
Character device major/minor: 242:4
-----------------------------------
Volume ID:   4 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        529 LEBs (134340608 bytes, 128.1 MiB)
State:       OK
Name:        data
Character device major/minor: 242:5


Thanks
--
Stephan Wurm <stephan.wurm@a-eberle.de>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2023-07-21  7:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  8:07 ubiblock: null pointer dereference using scatterlist in work_queue Stephan Wurm
2023-07-17  9:42 ` Richard Weinberger
2023-07-17 10:27   ` Stephan Wurm
2023-07-17 11:03     ` Richard Weinberger
2023-07-17 14:55       ` Stephan Wurm
2023-07-17 20:54         ` Richard Weinberger
2023-07-19 14:31         ` Richard Weinberger
2023-07-19 14:38           ` Wurm, Stephan
2023-07-21  7:41             ` Wurm, Stephan [this message]
2023-08-07 22:02 ` Richard Weinberger
2023-08-09 13:53   ` hch
2023-08-09 14:10     ` Stephan Wurm
2023-08-09 14:15       ` hch
2023-08-09 22:34         ` Richard Weinberger
2023-08-09 22:37           ` hch
2023-08-09 22:43             ` Richard Weinberger
2023-08-10 15:43               ` hch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZLo2rpBa+MiHaIR1@PC-LX-Wurm \
    --to=stephan.wurm@a-eberle.de \
    --cc=Johannes.Eigner@a-eberle.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox