diff options
| author | Jose Alonso <joalonsof@gmail.com> | 2014-01-28 08:09:46 -0700 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2014-01-28 08:09:46 -0700 |
| commit | 0d0b7d427987f6e98b6f32e84ee071f36f85c3d4 (patch) | |
| tree | 49e20246644048c004f1b1d3c95440538465a12b /block/blk-mq-cpu.c | |
| parent | 17a05cca99d952f5b4766fa48a2703548966636a (diff) | |
| download | linux-stable-0d0b7d427987f6e98b6f32e84ee071f36f85c3d4.tar.gz linux-stable-0d0b7d427987f6e98b6f32e84ee071f36f85c3d4.tar.bz2 linux-stable-0d0b7d427987f6e98b6f32e84ee071f36f85c3d4.zip | |
blk-mq: for_each_* macro correctness
I observed that there are for_each macros that do an extra memory access
beyond the defined area.
Normally this does not cause problems.
But, this can cause exceptions. For example: if the area is allocated at
the end of a page and the next page is not accessible.
For correctness, I suggest changing the arguments of the 'for loop' like
others 'for_each' do in the kernel.
Signed-off-by: Jose Alonso <joalonsof@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-mq-cpu.c')
0 files changed, 0 insertions, 0 deletions