Re: [systemd-devel] Clarification around a segmentation fault from an udevd worker

2015-07-26 Thread SF Markus Elfring 
 It should print the backtrace with the location where the error happened.

Unfortunately, no.


Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop systemd-udevd.service 
systemd-udevd-kernel.socket systemd-udevd-control.socket  gdb systemd-udevd
…
worker [5347] terminated by signal 11 (Segmentation fault)
worker [5347] failed while handling 
'/devices/pci:00/:00:02.0/usb3/3-2/3-2:1.0'
udev_monitor_send_device:/home/elfring/Projekte/systemd/lokal/src/libudev/libudev-monitor.c:770:
 passed device to netlink monitor 0x55671520
^CUnloaded link configuration context.
[Inferior 1 (process 5339) exited normally]
(gdb) bt full
No stack.


Sonne:~ # journalctl -xe
…
Jul 26 15:03:38 Sonne systemd-udevd[5347]: audit-1701 auid=1000 uid=0 gid=0 
ses=1 pid=5347 comm=systemd-udevd 
exe=/home/elfring/Projekte/Bau/systemd/systemd-udevd sig
Jul 26 15:03:38 Sonne kernel: systemd-udevd[5347]: segfault at 438 ip 
76fefc78 sp 7fffc6b0 error 4 in 
libc-2.21.so[76fa7000+196000]
…


Do I need to be more concerned about an error 4?

Regards,
Markus
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Clarification around a segmentation fault from an udevd worker

2015-07-26 Thread Kay Sievers 
On Sun, Jul 26, 2015 at 3:22 PM, SF Markus Elfring
elfr...@users.sourceforge.net wrote:
 It should print the backtrace with the location where the error happened.

 Unfortunately, no.


 Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop 
 systemd-udevd.service systemd-udevd-kernel.socket 
 systemd-udevd-control.socket  gdb systemd-udevd
 …
 worker [5347] terminated by signal 11 (Segmentation fault)
 worker [5347] failed while handling 
 '/devices/pci:00/:00:02.0/usb3/3-2/3-2:1.0'
 udev_monitor_send_device:/home/elfring/Projekte/systemd/lokal/src/libudev/libudev-monitor.c:770:
  passed device to netlink monitor 0x55671520
 ^CUnloaded link configuration context.
 [Inferior 1 (process 5339) exited normally]
 (gdb) bt full
 No stack.


 Sonne:~ # journalctl -xe
 …
 Jul 26 15:03:38 Sonne systemd-udevd[5347]: audit-1701 auid=1000 uid=0 gid=0 
 ses=1 pid=5347 comm=systemd-udevd 
 exe=/home/elfring/Projekte/Bau/systemd/systemd-udevd sig
 Jul 26 15:03:38 Sonne kernel: systemd-udevd[5347]: segfault at 438 ip 
 76fefc78 sp 7fffc6b0 error 4 in 
 libc-2.21.so[76fa7000+196000]

Does:
  $ addr2line -e home/elfring/Projekte/Bau/systemd/systemd-udevd
0x76fefc78

show something?

Thanks,
Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] udev and dm inotify problems

2015-07-26 Thread Oleksii Shevchuk 
Andrei Borzenkov arvidj...@gmail.com writes:


 Could you verify with e.g. inotifywatch whether inotify event was
 generated by kernel?


It turns out, that for some reason I have several dm devices:

# ls -l /dev/mapper/
crw-rw 1 root dialout  10, 236 ??? 25 09:52 control
brw--- 1 root root254,  12 ??? 25 09:52 _dev_dm_5
lrwxrwxrwx 1 root root   7 ??? 25 09:52 Media-Doc - ../dm-3
lrwxrwxrwx 1 root root   7 ??? 25 09:52 Media-Music - ../dm-1
lrwxrwxrwx 1 root root   7 ??? 25 09:52 Media-Tmp - ../dm-2
lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-home - ../dm-5
lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-kernel - ../dm-7
lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-portage - ../dm-4
lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-prefix - ../dm-8
brw--- 1 root root254,   0 ??? 25 09:52 OS-root
lrwxrwxrwx 1 root root   8 ??? 25 09:52 OS-Software - ../dm-10
lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-var - ../dm-9
lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-VM - ../dm-6
brw--- 1 root root254,  11 ??? 26 11:36 swap  SWAP is here

Also I have separate device - /dev/dm-11, with same major/minor.

inotifywait get CLOSE_WRITE events only when the same device file is used.

// wbr
// Oleksii Shevchuk
 ___
 systemd-devel mailing list
 systemd-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Clarification around a segmentation fault from an udevd worker

2015-07-26 Thread SF Markus Elfring 
 Jul 26 15:03:38 Sonne systemd-udevd[5347]: audit-1701 auid=1000 uid=0 
 gid=0 ses=1 pid=5347 comm=systemd-udevd 
 exe=/home/elfring/Projekte/Bau/systemd/systemd-udevd sig
 Jul 26 15:03:38 Sonne kernel: systemd-udevd[5347]: segfault at 438 ip 
 76fefc78 sp 7fffc6b0 error 4 in 
 libc-2.21.so[76fa7000+196000]
 
 Does:
   $ addr2line -e home/elfring/Projekte/Bau/systemd/systemd-udevd 
 0x76fefc78
 
 show something?

Not the information we are interested in.


Sonne:~ # addr2line -e /home/elfring/Projekte/Bau/systemd/systemd-udevd 
0x76fefc78
??:0


Is such a display useful for a corresponding problem analysis?

Regards,
Markus
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Creation of additional links for selected devices

2015-07-26 Thread SF Markus Elfring 
Hello,

I would like to clarify the combination of commands like
udevadm control -p and udevadm trigger a bit more.

How do device properties differ from attributes in this
use case?

I imagine that additional properties can be set before
a corresponding addition of matching devices would
be triggered. Would you like to share any more experiences
around the fine-tuning of such settings and their reuse
for the generation of symbolic links by udev rules?

Regards,
Markus
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Creation of additional links for selected devices

2015-07-26 Thread Mantas Mikulėnas 
On Sun, Jul 26, 2015 at 6:50 PM, SF Markus Elfring 
elfr...@users.sourceforge.net wrote:

 Hello,

 I would like to clarify the combination of commands like
 udevadm control -p and udevadm trigger a bit more.


Hmm, I'm not sure when `control -p` could ever be useful...


 How do device properties differ from attributes in this
 use case?


Properties (sometimes called environment) are held in udev's database; they
can be set via ENV{} or imported from helpers (e.g. hwdb, blkid...).

Attributes correspond directly to files in sysfs; they can be read or set
via ATTR{}, but you're always limited to only the information exported by
the *kernel*.


 I imagine that additional properties can be set before
 a corresponding addition of matching devices would
 be triggered. Would you like to share any more experiences
 around the fine-tuning of such settings and their reuse
 for the generation of symbolic links by udev rules?


...??

-- 
Mantas Mikulėnas graw...@gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Completion of error handling

2015-07-26 Thread SF Markus Elfring 
 No, nothing needs more discussion or attention in the context of systemd.

I disagree here. - I would appreciate if return value ignorance can be still
reduced at more source code places.

Do you distinguish any update candidates which belong to a subsystem
in this software?


 None of the above seems contain anything useful or is expected to
 contribute anything useful in the future.

More time will pass by until the adoption of higher level tools might increase.

Changes can be introduced by file formats which need some manual work.
Would it be nice if a software evolution pattern should only be specified once
and can be applied to a wide range of source files then automatically?


 This is a development mailing list, we discuss patches and actual code,
 and not vague questions like you ask.

Do any updates need a bit of consensus before big efforts will be invested.

Will any software developer (besides me) become interested to integrate
a patch in the format of an AspectC++ file or a SmPL script for example?

Regards,
Markus
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] udev and dm inotify problems

2015-07-26 Thread Andrei Borzenkov 
В Sun, 26 Jul 2015 11:39:17 +0300
Oleksii Shevchuk alx...@gmail.com пишет:

 Andrei Borzenkov arvidj...@gmail.com writes:
 
 
  Could you verify with e.g. inotifywatch whether inotify event was
  generated by kernel?
 
 
 It turns out, that for some reason I have several dm devices:
 
 # ls -l /dev/mapper/
 crw-rw 1 root dialout  10, 236 ??? 25 09:52 control
 brw--- 1 root root254,  12 ??? 25 09:52 _dev_dm_5
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 Media-Doc - ../dm-3
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 Media-Music - ../dm-1
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 Media-Tmp - ../dm-2
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-home - ../dm-5
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-kernel - ../dm-7
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-portage - ../dm-4
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-prefix - ../dm-8
 brw--- 1 root root254,   0 ??? 25 09:52 OS-root
 lrwxrwxrwx 1 root root   8 ??? 25 09:52 OS-Software - ../dm-10
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-var - ../dm-9
 lrwxrwxrwx 1 root root   7 ??? 25 09:52 OS-VM - ../dm-6
 brw--- 1 root root254,  11 ??? 26 11:36 swap  SWAP is here
 
 Also I have separate device - /dev/dm-11, with same major/minor.
 
 inotifywait get CLOSE_WRITE events only when the same device file is used.

So that it the problem. Does it happen if you use cryptsetup directly?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel