| 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
| ||
|
Message-ID: <20071022133723.089b84db@gondolin.boeblingen.de.ibm.com> Date: Mon, 22 Oct 2007 13:37:23 +0200 From: Cornelia Huck <cornelia.huck@...ibm.com> To: emist <emistz@...il.com> Cc: Linux <linux-kernel@...r.kernel.org>, geraldsc@...ibm.com, cotte@...ibm.com, linux390@...ibm.com, linux-s390@...r.kernel.org, Tejun Heo <htejun@...il.com> Subject: Re: [PATCH] Bug fix for the s390 dcssblk driver On Sun, 21 Oct 2007 23:46:49 -0400, emist <emistz@...il.com> wrote: > # This patch fixes a memory corruption bug in the s390 dcssblk driver. > # The bug occurs when an attempt to change the type of a segment > # returns an error. At this point the driver tries to remove the segment in > # question while some of the device's attributes are in use. This causes the > # driver to hang. Hm, seems we missed another of those device attributes exhibiting suicidal tendencies... Tejun has a patchset allowing device attributes to commit suicide (see http://marc.info/?l=linux-kernel&m=119027371416452&w=2), although I'm not sure what its current status is. Until then, you would need to use device_schedule_callback() to commit suicide. This all of course only applies if killing the segment is better than leaving it in its current state, but others can make a better judgement on that :) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists