summaryrefslogtreecommitdiffstats
path: root/vpnor/test/write_rw.cpp
diff options
context:
space:
mode:
authorAndrew Jeffery <andrew@aj.id.au>2018-03-27 10:35:31 +1030
committerAndrew Jeffery <andrew@aj.id.au>2018-04-04 17:27:31 +0930
commit52a8319658c8ac3dcce2fed116d20d6014d7b143 (patch)
treec546f26c8d07e3284828b09d85574d3806cd1c1c /vpnor/test/write_rw.cpp
parent943aba060f143667d502792f11e95f42bc7da346 (diff)
downloadphosphor-mboxd-52a8319658c8ac3dcce2fed116d20d6014d7b143.tar.gz
phosphor-mboxd-52a8319658c8ac3dcce2fed116d20d6014d7b143.zip
vpnor: Add handler for CREATE_WRITE_WINDOW
The virtual PNOR implementation enforces the read-only attribute of FFS partitions, which is a departure from how things were handled previously. In the past it was purely up to the host to respect the flags set on the partition, but nothing prevented the host from modifying it. Now it's possible for errors to occur when the host attempts to flush changes back to the flash: mboxd can deny the change. This denial can happen in a number of circumstances: 1. An explicit WRITE_FLUSH command from the host 2. An implicit WRITE_FLUSH via an explicit CLOSE_WINDOW command 3. An implicit WRITE_FLUSH via CREATE_{READ,WRITE}_WINDOW, which happens via the implicit CLOSE_WINDOW All of these attempts will fail if the write to the currently open window cannot be allowed to succeed. Failing to open a read window due to failure to flush pending writes is particularly painful, as we are not able to ever successfully open a window again. Instead, detect when the host attempts to open a write window over a anything but a writeable partition. If this case is detected, return an error for the CREATE_WRITE_WINDOW operation to prevent systemic failures later on. Change-Id: I991b6f1570d9b1b384b1024e3bd8a77e5efcd198 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Diffstat (limited to 'vpnor/test/write_rw.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud