On 6/20/24 15:32, Ulf Hansson wrote: > On Thu, 20 Jun 2024 at 14:59, Daniel Kucera <linux-mmc@xxxxxxxxx> wrote: >> >> On 2024-06-20 14:38, Ulf Hansson wrote: >>> On Thu, 6 Jun 2024 at 15:12, <linux-mmc@xxxxxxxxx> wrote: >>>> >>>> From: Daniel Kucera <linux-mmc@xxxxxxxxx> >>>> >>>> Locked SD card will not reply to SEND_SCR or SD_STATUS commands >>>> so it was failing to initialize previously. When skipped, >>>> the card will get initialized and CMD42 can be sent using >>>> ioctl to unlock the card or remove password protection. >>>> For eMMC, this is not necessary because all initialization >>>> commands are allowed in locked state. >>>> Until unlocked, all read/write calls will timeout. >>> >>> Skipping the commands above, only means the card gets partially >>> initialized. >> >> Correct, but it's an improvement in comparison to current state. > > Not sure I agree with that, sorry. > >> >>> Leaving a card in that state seems fragile. >> >> Fragile in what sense? Nothing can happen to the card as it is locked. > > We may end up having a card half-way initialized that we can't really > communicate with in a stable manner. From a system point of view, I > would be worried. > > I would rather just power off the card if initialization fails and > remove its corresponding device from the system. > >> >>> What will >>> happen to upper block layers and filesystems when trying to access it? >> >> Everything will simply time-out. > > Yes, but it's uncertain what that could lead to? > > What will happen with power consumption and power management support, > for example. Definitely an aspect that needs to be considered, probably even just powering it off after 10ish seconds would be better, then you still get the chance of unlocking it without having a locked card unknowingly consuming power. Having a saved key and sending that to any card being plugged in seems wrong if you consider security, then again if you consider security you should probably somewhere else than the SD/MMC LOCK/UNLOCK ;) Kind Regards, Christian
