I/O issues with writing to mtdblock devices on kirkwood

Mark Brown
2016-01-12T01:31:40Z

On Tue, Jan 12, 2016 at 02:19:04AM +0100, Andrew Lunn wrote:

> When i played with this, i added a reschedule point at the end of the
> drivers transfer_one_message() function, to see if that would help. It
> did not, which is why i made a guess it has something to do with a
> lock.

The SPI core doesn't hold any locks while it pushes things into the
driver. It has a spin lock to queue and deque messages but it drops
that before it hands off to the driver (many of which sleep so we'd
expect people to notice if we forgot to drop the lock). It's possible
there's something going on there but I'd be very surprised if we messed
up the locking and only managed to notice over a period of years via an
interaction with another subsystem with no direct ties...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160112/bac3e762/attachment.sig>