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
| ||
|
Date: Thu, 7 May 2020 15:44:23 +0800 From: Ming Lei <ming.lei@...hat.com> To: Christoph Hellwig <hch@....de> Cc: axboe@...nel.dk, yuyufen@...wei.com, tj@...nel.org, jack@...e.cz, bvanassche@....org, tytso@....edu, hdegoede@...hat.com, gregkh@...uxfoundation.org, linux-block@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: bdi: fix use-after-free for dev_name(bdi->dev) v3 (resend) On Mon, May 04, 2020 at 02:47:52PM +0200, Christoph Hellwig wrote: > Hi Jens, > > can you pick up this series? > > the first three patches are my take on the proposal from Yufen Yu > to fix the use after free of the device name of the bdi device. > > The rest is vaguely related cleanups. > > Changes since v2: > - switch vboxsf to a shorter bdi name > > Changes since v1: > - use a static dev_name buffer inside struct backing_dev_info > Looks fine: Reviewed-by: Ming Lei <ming.lei@...hat.com> -- Ming
Powered by blists - more mailing lists