From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Re: Hotplug events during sleep transition Date: Fri, 23 Dec 2005 23:31:42 +0100 Message-ID: <20051223223142.GA16104@elf.ucw.cz> References: <20051223172057.GA15357@elf.ucw.cz> <20051223212827.GA17350@kroah.com> <1135375796.9616.155.camel@localhost> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============083505333287928973==" Return-path: In-Reply-To: <1135375796.9616.155.camel@localhost> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Nigel Cunningham Cc: Linux-pm mailing list List-Id: linux-pm@vger.kernel.org --===============083505333287928973== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! > > > > Well, if you can find some elegant solution in the core, I think thats > > > > the best way. > > > > > > > > You could set system_state to "suspending" or something like that, and > > > > just if() out notifications in that case. > > > > > > How about simply adding a call to try_to_freeze() somewhere inside > > > kernel/kmod.c:____call_usermodehelper()? That ought to do pretty much > > > what I want, in theory. The hotplug processes would get frozen before > > > /sbin/hotplug is exec'ed. > > > > On modern distros, /sbin/hotplug is set to NULL, so this isn't an issue. > > We use netlink to send the data out, so this might not even be a problem > > anymore... > > At resume time, prior to copying back the original kernel data, events > can and do occur. > > FWIW, I've been using "if(freezer_is_on()) return 0" for a while in > call_usermodehelper_keys, to good effect. Can we have a patch? Pavel -- Thanks, Sharp! --===============083505333287928973== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============083505333287928973==--