Coly Li
09a44ca211
bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set
...
It is possible that multiple I/O requests hits on failed cache device or
backing device, therefore it is quite common that CACHE_SET_IO_DISABLE is
set already when a task tries to set the bit from bch_cache_set_error().
Currently the message "CACHE_SET_IO_DISABLE already set" is printed by
pr_warn(), which might mislead users to think a serious fault happens in
source code.
This patch uses pr_info() to print the information in such situation,
avoid extra worries. This information is helpful to understand bcache
behavior in cache device failures, so I still keep them in source code.
Fixes: 771f393e8f
("bcache: add CACHE_SET_IO_DISABLE to struct cache_set flags")
Signed-off-by: Coly Li <colyli@suse.de >
Reviewed-by: Hannes Reinecke <hare@suse.com >
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2018-05-03 08:35:16 -06:00
..
2018-05-03 08:35:16 -06:00
2018-04-03 15:04:23 -04:00
2017-06-19 11:03:50 -04:00
2017-06-09 09:27:32 -06:00
2017-06-19 11:03:50 -04:00
2017-03-07 11:30:16 -05:00
2017-08-23 12:49:55 -06:00
2018-04-03 15:04:29 -04:00
2017-11-02 11:10:55 +01:00
2017-11-10 15:45:03 -05:00
2017-03-07 13:28:31 -05:00
2016-12-16 00:13:41 +02:00
2017-10-24 15:09:51 -04:00
2017-03-07 13:28:31 -05:00
2017-03-07 13:28:31 -05:00
2017-11-10 15:45:05 -05:00
2014-01-16 13:44:11 -05:00
2017-03-07 13:28:31 -05:00
2018-04-03 15:04:10 -04:00
2018-01-29 13:44:55 -05:00
2018-04-03 15:04:11 -04:00
2018-01-17 09:16:15 -05:00
2018-04-03 15:04:10 -04:00
2015-11-04 21:19:53 -08:00
2016-01-08 20:03:05 -05:00
2018-04-04 12:12:39 -04:00
2018-04-03 15:04:23 -04:00
2017-12-13 12:15:56 -05:00
2018-04-03 15:04:10 -04:00
2018-01-17 09:16:15 -05:00
2018-04-10 10:25:57 -07:00
2015-10-31 19:06:00 -04:00
2015-04-15 12:10:20 -04:00
2018-04-10 10:25:57 -07:00
2016-11-01 09:43:26 -06:00
2018-04-04 12:12:39 -04:00
2016-02-22 22:34:42 -05:00
2018-01-29 13:44:58 -05:00
2017-11-14 20:11:57 -07:00
2018-04-04 12:12:37 -04:00
2016-08-07 14:41:02 -06:00
2017-02-17 00:54:09 -05:00
2018-02-04 11:16:35 -08:00
2017-08-28 10:23:28 -04:00
2018-01-29 13:44:58 -05:00
2018-04-03 15:04:23 -04:00
2016-01-08 20:03:05 -05:00
2018-01-17 09:16:14 -05:00
2018-01-17 09:16:15 -05:00
2017-11-02 11:10:55 +01:00
2018-04-10 10:25:57 -07:00
2018-04-04 12:12:39 -04:00
2016-06-10 15:15:44 -04:00
2018-04-06 11:50:19 -07:00
2018-04-03 15:04:15 -04:00
2018-01-17 09:07:54 -05:00
2016-07-20 12:43:35 -04:00
2018-04-03 15:04:10 -04:00
2018-04-03 15:04:15 -04:00
2017-07-26 15:55:44 -04:00
2017-03-16 09:37:31 -04:00
2018-04-04 12:12:39 -04:00
2018-04-03 15:04:29 -04:00
2017-06-09 09:27:32 -06:00
2018-01-17 09:16:15 -05:00
2017-07-26 15:55:43 -04:00
2018-04-04 12:12:39 -04:00
2017-06-19 11:05:20 -04:00
2018-04-10 10:25:57 -07:00
2018-01-17 09:16:06 -05:00
2018-04-03 05:41:19 -07:00
2018-01-17 09:16:00 -05:00
2017-11-14 16:07:26 -08:00
2017-11-14 16:07:26 -08:00
2017-11-01 21:32:25 -07:00
2017-11-02 11:10:55 +01:00
2017-10-16 19:06:36 -07:00
2018-03-08 14:13:48 -07:00
2017-11-14 16:07:26 -08:00
2018-02-17 13:00:35 -08:00
2017-11-14 16:07:26 -08:00
2018-04-09 08:39:36 -07:00
2018-02-18 10:11:59 -08:00
2018-03-08 14:13:48 -07:00
2017-11-02 11:10:55 +01:00
2017-11-02 11:10:55 +01:00
2018-04-09 08:54:34 -07:00
2018-02-18 10:22:27 -08:00
2018-01-15 14:29:42 -08:00
2018-02-21 09:40:40 -08:00
2018-02-21 09:40:40 -08:00
2018-04-05 14:27:02 -07:00
2018-02-18 10:22:27 -08:00
2018-04-05 14:27:02 -07:00
2018-02-18 10:22:27 -08:00