Re: [PATCH -next v2] block: fix blktrace debugfs entries leak

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Yu Kuai <yukuai1@xxxxxxxxxxxxxxx>
Subject: Re: [PATCH -next v2] block: fix blktrace debugfs entries leak
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 31 May 2023 14:44:04 +0200
Cc: hch@xxxxxx, axboe@xxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, yukuai3@xxxxxxxxxx, yi.zhang@xxxxxxxxxx, yangerkun@xxxxxxxxxx
In-reply-to: <20230531092606.3037560-1-yukuai1@huaweicloud.com>
References: <20230531092606.3037560-1-yukuai1@huaweicloud.com>
User-agent: Mutt/1.5.17 (2007-11-01)

I like where this is going, but did you check that this doesn't
introduce a potential crash with the current /dev/sg based blktrace?

Follow-Ups:
- Re: [PATCH -next v2] block: fix blktrace debugfs entries leak
  - From: Yu Kuai

References:
- [PATCH -next v2] block: fix blktrace debugfs entries leak
  - From: Yu Kuai

Prev by Date: Re: [PATCH v7 20/20] block: mark bio_add_folio as __must_check
Next by Date: [PATCH net-next v2 1/6] splice, net: Fix MSG_MORE signalling in splice_direct_to_actor()
Previous by thread: [PATCH -next v2] block: fix blktrace debugfs entries leak
Next by thread: Re: [PATCH -next v2] block: fix blktrace debugfs entries leak
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux