WireClient: MapReadCallback, unconditionnally consume the data
WireClient: MapReadCallback, unconditionnally consume the data

When a MapReadRequestCallback arrived late and hit one of the early out
of the handler (for example if the buffer was already unmapped), the
handler wouldn't consume the data payload of the command. This would
cause the command buffer pointer to not be advanced enough and point to
random data instead of the next command.

googlearchive/nxt-standalone,googlearchive/nxt-standalone,Kangz/nxt-standalone,googlearchive/nxt-standalone,googlearchive/nxt-standalone,Kangz/nxt-standalone,Kangz/nxt-standalone,Kangz/nxt-standalone