HI! > > Why not simply &~ PF_NOFREEZE on that particular process? Filesystems > > are free to use threads/work queues/whatever, but refrigerator should > > mean "no writes to filesystem" for them... > > You can't go around altering the flags of another process - what locking > are you relying upon for this ? Well, my idea was for process to &~ PF_NOFREEZE on itself. We are currently (kernel/power/process.c) using &p->sighand->siglock for some accesses, and no locking for others. There were some attempts to fix this, but they led to problems, and we are not hitting any problems... part of reason is that we hot-unplug non-boot cpus before freezing processes, so we are running UP at that point. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
