[Bug 1734681] Re: Parted accessing {mmcblk, ...}[0-9]rpmb considered a bug?

[Phillip Susi]

I can't seem to find any documentation on these block devices,
specifically how to recognize one.  Can you list the contents of the
sysfs node for one?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to parted in Ubuntu.
https://bugs.launchpad.net/bugs/1734681

Title:
  Parted accessing {mmcblk,...}[0-9]rpmb considered a bug?

Status in parted package in Ubuntu:
  New

Bug description:
  eMMC spec 4.5 allows a tiny (typically 2MiB or 4MiB in size) Replay
  Protected Memory Block. MMC as well as UFS and NVMe have support for
  RPMB's. That RPMB area is protected from any read and write access.

  An example:
  $ dmesg | grep rpmb
  [    6.712468] mmcblk0rpmb: mmc0:0001 SEM04G partition 3 2.00 MiB

  The kernel has been patched to not access this rpmb area.
  [1] <http://lkml.iu.edu/hypermail/linux/kernel/1604.0/01227.html>
  Dmesg doesn't output any errors during boot.

  However parted (GNU parted) 3.2 still tries to access the RPMB area,
  resulting in:

  Error: /dev/mmcblk0rpmb: unrecognised disk label
  Warning: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error
  Retry/Ignore?

  And in dmesg errors like this are logged:

  [46684.715228] print_req_error: I/O error, dev mmcblk0rpmb, sector 0

  Should (GNU) parted be patched too, or not?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1734681/+subscriptions