lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <509bcea6-21f6-3f64-01c3-02215955283d@huaweicloud.com>
Date:   Thu, 1 Jun 2023 09:50:22 +0800
From:   Yu Kuai <yukuai1@...weicloud.com>
To:     Christoph Hellwig <hch@....de>, Yu Kuai <yukuai1@...weicloud.com>
Cc:     axboe@...nel.dk, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org, yi.zhang@...wei.com,
        yangerkun@...wei.com, "yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH -next v2] block: fix blktrace debugfs entries leak

Hi, Christoph

在 2023/05/31 20:44, Christoph Hellwig 写道:
> 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?

I just start to look at how /dev/sg is created and destroyed, however,
I'm confused here, do you mean that the added blk_trace_shutdown() here
might cause that /dev/sg blktrace to access freed momory or NULL
pointer?

Thanks,
Kuai
> 
> 
> .
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ