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: Wed, 29 Mar 2017 11:23:08 -0400 From: Tejun Heo <tj@...nel.org> To: Johannes Thumshirn <jthumshirn@...e.de> Cc: "Martin K . Petersen" <martin.petersen@...cle.com>, James Bottomley <jejb@...ux.vnet.ibm.com>, Dan Williams <dan.j.williams@...el.com>, John Garry <john.garry@...wei.com>, Jack Wang <jinpu.wang@...fitbricks.com>, Hannes Reinecke <hare@...e.de>, Linux SCSI Mailinglist <linux-scsi@...r.kernel.org>, Linux Kernel Mailinglist <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 0/2] Fix sysfs recursive removal splats in isci Hello, On Wed, Mar 29, 2017 at 11:41:07AM +0200, Johannes Thumshirn wrote: > This series fixes a sysfs warning caused by isci not being able to cope with > recursive sysfs path removals which are in place since commit bcdde7e > ("sysfs: make __sysfs_remove_dir() recursive"). Thanks for fixing these. > The mvsas, aic94xx and pm8001 and hisi_sas patches have been compile tested > only hence they have no callstack of the affected path in their changelogs. > > I'm not sure whether to mark this patches as stable or not. I tend to say no > here, although we've seen complaints/bug reports on lkml and the scsi list. Given that the failures aren't critical or all that common (only happens on controller removal), I agree that not cc'ing stable is the right call here. Thanks. -- tejun
Powered by blists - more mailing lists