Re: [PATCH] bcache: not access dc->bdev when backing device is offline

Hi Coly, >On 2018/4/16 4:56 PM, tang.jun...@zte.com.cn wrote: >> Hi Coly, >> >>> When backing device is offline, memory object pointed by dc->bdev might be >>> released in some condititions. I have bug report that bdevname() triggers >>> a NULL pointer deference panic inside bch_cached_dev_error(

Re: [PATCH] bcache: not access dc->bdev when backing device is offline

On 2018/4/16 4:56 PM, tang.jun...@zte.com.cn wrote: > Hi Coly, > >> When backing device is offline, memory object pointed by dc->bdev might be >> released in some condititions. I have bug report that bdevname() triggers >> a NULL pointer deference panic inside bch_cached_dev_error(), where >> dc->

Re: [PATCH] bcache: not access dc->bdev when backing device is offline

Hi Coly, >When backing device is offline, memory object pointed by dc->bdev might be >released in some condititions. I have bug report that bdevname() triggers >a NULL pointer deference panic inside bch_cached_dev_error(), where >dc->bdev is NULL. > >This patch adds char backing_dev_name[BDEVNAME_

[PATCH] bcache: not access dc->bdev when backing device is offline

When backing device is offline, memory object pointed by dc->bdev might be released in some condititions. I have bug report that bdevname() triggers a NULL pointer deference panic inside bch_cached_dev_error(), where dc->bdev is NULL. This patch adds char backing_dev_name[BDEVNAME_SIZE] in struct