On Sun, Jan 15, 2023 at 01:27:09AM +0300, Fedor Pchelkin wrote:
From: Christoph Hellwig hch@lst.de
commit 57e95e4670d1126c103305bcf34a9442f49f6d6a upstream.
Don't use a WARN_ONCE when printing a potentially user triggered condition.
Signed-off-by: Christoph Hellwig hch@lst.de Reviewed-by: Chaitanya Kulkarni kch@nvidia.com Reviewed-by: Johannes Thumshirn johannes.thumshirn@wdc.com Link: https://lore.kernel.org/r/20220304180105.409765-2-hch@lst.de Signed-off-by: Jens Axboe axboe@kernel.dk Signed-off-by: Fedor Pchelkin pchelkin@ispras.ru
block/blk-core.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/block/blk-core.c b/block/blk-core.c index 26664f2a139e..921d436fa3c6 100644 --- a/block/blk-core.c +++ b/block/blk-core.c @@ -701,8 +701,7 @@ static inline bool bio_check_ro(struct bio *bio, struct hd_struct *part) if (op_is_flush(bio->bi_opf) && !bio_sectors(bio)) return false;
WARN_ONCE(1,"Trying to write to read-only block-device %s (partno %d)\n",
pr_warn("Trying to write to read-only block-device %s (partno %d)\n", bio_devname(bio, b), part->partno);-- 2.34.1
Again, we CAN NOT take patches for older kernels and not for newer ones, that one will cause regressions when people upgrade to newer kernels.
So I'm dropping all of your patches from my queue, please resend them so that all trees are properly covered. As-is, I can not take the, and most importantly, you do not want me to accept such a thing!
thanks,
greg k-h