diff options
| author | Eric Biggers <ebiggers@google.com> | 2020-09-15 20:53:15 -0700 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2020-10-05 10:47:43 -0600 |
| commit | cf785af19319f9fc0fc0c0604d259f1ef31b502f (patch) | |
| tree | b047fc45f79597a6943d9408e66a376483c4b5c3 /drivers/scsi/pcmcia/nsp_cs.h | |
| parent | 93f221ae08381e994ac9f9ff6aa743e612e49718 (diff) | |
| download | linux-cf785af19319f9fc0fc0c0604d259f1ef31b502f.tar.gz linux-cf785af19319f9fc0fc0c0604d259f1ef31b502f.tar.bz2 linux-cf785af19319f9fc0fc0c0604d259f1ef31b502f.zip | |
block: warn if !__GFP_DIRECT_RECLAIM in bio_crypt_set_ctx()
bio_crypt_set_ctx() assumes its gfp_mask argument always includes
__GFP_DIRECT_RECLAIM, so that the mempool_alloc() will always succeed.
For now this assumption is still fine, since no callers violate it.
Making bio_crypt_set_ctx() able to fail would add unneeded complexity.
However, if a caller didn't use __GFP_DIRECT_RECLAIM, it would be very
hard to notice the bug. Make it easier by adding a WARN_ON_ONCE().
Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Satya Tangirala <satyat@google.com>
Cc: Miaohe Lin <linmiaohe@huawei.com>
Cc: Satya Tangirala <satyat@google.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/scsi/pcmcia/nsp_cs.h')
0 files changed, 0 insertions, 0 deletions