linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* udev signal handler should not syslog()
@ 2004-11-02 15:43 Harald Hoyer
  2004-11-02 15:50 ` Harald Hoyer
  2004-11-02 23:42 ` Kay Sievers
  0 siblings, 2 replies; 3+ messages in thread
From: Harald Hoyer @ 2004-11-02 15:43 UTC (permalink / raw)
  To: linux-hotplug

[-- Attachment #1: Type: text/plain, Size: 211 bytes --]

Please remove any syslog() from the signal handler!
According to
http://www.opengroup.org/onlinepubs/000095399/functions/xsh_chap02_04.html
this is unsafe and we see hangups in vmware where SIGALRM is fired up.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: udev signal handler should not syslog()
  2004-11-02 15:43 udev signal handler should not syslog() Harald Hoyer
@ 2004-11-02 15:50 ` Harald Hoyer
  2004-11-02 23:42 ` Kay Sievers
  1 sibling, 0 replies; 3+ messages in thread
From: Harald Hoyer @ 2004-11-02 15:50 UTC (permalink / raw)
  To: linux-hotplug

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

Harald Hoyer wrote:
> Please remove any syslog() from the signal handler!
> According to
> http://www.opengroup.org/onlinepubs/000095399/functions/xsh_chap02_04.html
> this is unsafe and we see hangups in vmware where SIGALRM is fired up.

the tdb_close() used in the signal handler, contains free() calls, which seem to be dangerous as well!

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: udev signal handler should not syslog()
  2004-11-02 15:43 udev signal handler should not syslog() Harald Hoyer
  2004-11-02 15:50 ` Harald Hoyer
@ 2004-11-02 23:42 ` Kay Sievers
  1 sibling, 0 replies; 3+ messages in thread
From: Kay Sievers @ 2004-11-02 23:42 UTC (permalink / raw)
  To: linux-hotplug

On Tue, Nov 02, 2004 at 04:43:19PM +0100, Harald Hoyer wrote:
> Please remove any syslog() from the signal handler!
> According to
> http://www.opengroup.org/onlinepubs/000095399/functions/xsh_chap02_04.html
> this is unsafe and we see hangups in vmware where SIGALRM is fired up.

Right, this should be fixed. I'll wait for a decision regarding the
tdb code. If the multi-file-db will work well for the thousands of
disks setup, all this stuff will go anyway.

udev_log="no" in /etc/udev/udev.conf should fix that in the meantime
for users running into trouble with that.

Thanks,
Kay



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-11-02 23:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-02 15:43 udev signal handler should not syslog() Harald Hoyer
2004-11-02 15:50 ` Harald Hoyer
2004-11-02 23:42 ` Kay Sievers

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).