summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorJohannes Thumshirn <jthumshirn@suse.de>2017-04-12 10:21:19 +0300
committerMartin K. Petersen <martin.petersen@oracle.com>2017-04-14 05:10:06 +0300
commite7661a8e5ce10b5321882d0bbaf3f81070903319 (patch)
tree07759b3cba1345ccadf86721fed578cb2bc9a580 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent785a470496d8e0a32e3d39f376984eb2c98ca5b3 (diff)
downloadlinux-e7661a8e5ce10b5321882d0bbaf3f81070903319.tar.xz
scsi: return correct blkprep status code in case scsi_init_io() fails.
When instrumenting the SCSI layer to run into the !blk_rq_nr_phys_segments(rq) case the following warning emitted from the block layer: blk_peek_request: bad return=-22 This happens because since commit fd3fc0b4d730 ("scsi: don't BUG_ON() empty DMA transfers") we return the wrong error value from scsi_prep_fn() back to the block layer. [mkp: silenced checkpatch] Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de> Fixes: fd3fc0b4d730 scsi: don't BUG_ON() empty DMA transfers Cc: <stable@vger.kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Hannes Reinecke <hare@suse.com> Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions