GNU logs - #29895, boring messages

Message sent to bug-parted@HIDDEN:

Subject: bug#29895: Parted 3.2 accessing /dev/mmcblk0rpmb considered a bug?
Resent-From: Ceriel Jacobs <linux-ide@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-parted@HIDDEN
Resent-Date: Fri, 29 Dec 2017 17:08:02 +0000
Resent-Message-ID: <handler.29895.B.15145672812973 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 29895 <at> debbugs.gnu.org
From: Ceriel Jacobs <linux-ide@HIDDEN>
Message-ID: <8f27a184-3dd5-e1db-c4d0-91dca115889f@HIDDEN>
Date: Fri, 29 Dec 2017 15:00:54 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:52.0)
 Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: nl
Content-Transfer-Encoding: 7bit
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

eMMC spec 4.5 has a tiny (2MiB or 4MiB) Replay Protected Memory Block.
As well as UFS and NVMe have support for RPMB.

That RPMB area is protected from readwrite access.

---
The kernel has been patched to not access this rpmb area:

$ dmesg | grep rpmb
[    6.712468] mmcblk0rpmb: mmc0:0001 SEM04G partition 3 2.00 MiB
---
Parted (GNU parted) 3.2 still tries to access the RPMB:

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

Resulting in dmesg logged errors like:

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

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

Cheers, Ceriel

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Ceriel Jacobs <linux-ide@HIDDEN>
Subject: bug#29895: Acknowledgement (Parted 3.2 accessing /dev/mmcblk0rpmb
 considered a bug?)
Message-ID: <handler.29895.B.15145672812973.ack <at> debbugs.gnu.org>
References: <8f27a184-3dd5-e1db-c4d0-91dca115889f@HIDDEN>
X-Gnu-PR-Message: ack 29895
X-Gnu-PR-Package: parted
Reply-To: 29895 <at> debbugs.gnu.org
Date: Fri, 29 Dec 2017 17:08:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-parted@HIDDEN

If you wish to submit further information on this problem, please
send it to 29895 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
29895: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D29895
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-parted@HIDDEN:

Subject: bug#29895: Parted 3.2 accessing /dev/mmcblk0rpmb considered a bug?
Resent-From: "Brian C. Lane" <bcl@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-parted@HIDDEN
Resent-Date: Tue, 02 Jan 2018 17:26:01 +0000
Resent-Message-ID: <handler.29895.B.151491394910035 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 29895 <at> debbugs.gnu.org
Date: Tue, 2 Jan 2018 09:25:31 -0800
From: "Brian C. Lane" <bcl@HIDDEN>
Message-ID: <20180102172531.GB32512@HIDDEN>
References: <8f27a184-3dd5-e1db-c4d0-91dca115889f@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8f27a184-3dd5-e1db-c4d0-91dca115889f@HIDDEN>
User-Agent: Mutt/1.9.1 (2017-09-22)
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

On Fri, Dec 29, 2017 at 03:00:54PM +0100, Ceriel Jacobs wrote:
> eMMC spec 4.5 has a tiny (2MiB or 4MiB) Replay Protected Memory Block.
> As well as UFS and NVMe have support for RPMB.
> 
> That RPMB area is protected from readwrite access.
> 
> ---
> The kernel has been patched to not access this rpmb area:
> 
> $ dmesg | grep rpmb
> [    6.712468] mmcblk0rpmb: mmc0:0001 SEM04G partition 3 2.00 MiB
> ---
> Parted (GNU parted) 3.2 still tries to access the RPMB:
> 
> Error: /dev/mmcblk0rpmb: unrecognised disk label
> Warning: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error
> Retry/Ignore?
> 
> Resulting in dmesg logged errors like:
> 
> [46684.715228] print_req_error: I/O error, dev mmcblk0rpmb, sector 0
> ---
> 
> Should (GNU) parted be patched too, or not?

What was the parted cmdline you were running?

And what are the permissions of the device node?

-- 
Brian C. Lane (PST8PDT)

Message sent to bug-parted@HIDDEN:

Subject: bug#29895: Parted 3.2 accessing /dev/mmcblk0rpmb considered a bug?
Resent-From: Phil Susi <psusi@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-parted@HIDDEN
Resent-Date: Wed, 14 Feb 2018 19:15:01 +0000
Resent-Message-ID: <handler.29895.B29895.151863569319568 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Ceriel Jacobs <linux-ide@HIDDEN>, 29895 <at> debbugs.gnu.org
References: <8f27a184-3dd5-e1db-c4d0-91dca115889f@HIDDEN>
From: Phil Susi <psusi@HIDDEN>
Message-ID: <ed86b5c5-159c-d424-7984-1321e8b3f2f4@HIDDEN>
Date: Wed, 14 Feb 2018 14:14:44 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <8f27a184-3dd5-e1db-c4d0-91dca115889f@HIDDEN>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

On 12/29/2017 9:00 AM, Ceriel Jacobs wrote:
> eMMC spec 4.5 has a tiny (2MiB or 4MiB) Replay Protected Memory Block.
> As well as UFS and NVMe have support for RPMB.

This came to my attention a while back elsewhere.. probably the debian
bug tracker.  The question is how to identify such a device so it can be
excluded?  Does it have a unique dev no?  Or some sysfs attribute that
flags it as an RPMB?

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.