| 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: <20100304135337.GC12191@atrey.karlin.mff.cuni.cz> Date: Thu, 4 Mar 2010 14:53:37 +0100 From: Pavel Machek <pavel@....cz> To: Alan Stern <stern@...land.harvard.edu> Cc: Jens Axboe <jens.axboe@...cle.com>, "Rafael J. Wysocki" <rjw@...k.pl>, Maxim Levitsky <maximlevitsky@...il.com>, linux-pm <linux-pm@...ts.linux-foundation.org>, linux-kernel <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [linux-pm] Is it supposed to be ok to call del_gendisk while userspace is frozen? Hi! > > journalling assumptions broken: commit block is there, but previous > > blocks are not intact. Data loss. > > > > ...and that was the first I could think about. Lets not do > > this. Barriers were invented for a reason. > > Very well. Then we still need a solution to the original problem: > Devices sometimes need to be unregistered during resume, but > del_gendisk() blocks on the writeback thread, which is frozen until > after the resume finishes. How do you suggest this be fixed? Avoid unregistering device during resume. Instead, return errors until resume is done and you can call del_gendisk? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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