Openembedded Core Discussions
 help / color / mirror / Atom feed
* udev ptest leaves symlink loops in target sysroots
@ 2014-09-15  5:10 Ed Swarthout
  2014-09-15 14:39 ` Burton, Ross
  0 siblings, 1 reply; 2+ messages in thread
From: Ed Swarthout @ 2014-09-15  5:10 UTC (permalink / raw)
  To: openembedded-core, alexandra.safta

I've been working on qemu crashes for the blacklisted emacs build.
As one of the fixes it would be nice to point qemu directly to the 
target sysroots directory to find the loader. But this causes qemu to 
hang because there are symlink loops in the directory tree and it does 
not know how to ignore loops.

It looks like udev ptest is the culprit:

/f/deb/home/yocto/yocto/build2014/tmp/sysroots/qemuppc/usr/lib/udev/ptest/test/sys/block/loop0/subsystem/loop0/subsystem:
   total used in directory 8 available 55515512
   drwxr-xr-x  2 ed ed0 4096 Aug 24 10:51 .
   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop0 -> 
../../devices/virtual/block/loop0
   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop1 -> 
../../devices/virtual/block/loop1
   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop2 -> 
../../devices/virtual/block/loop2
   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop3 -> 
../../devices/virtual/block/loop3

Does it have to leave these there after it completes the test?

Ed

Ed Swarthout
Austin, Tx


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

* Re: udev ptest leaves symlink loops in target sysroots
  2014-09-15  5:10 udev ptest leaves symlink loops in target sysroots Ed Swarthout
@ 2014-09-15 14:39 ` Burton, Ross
  0 siblings, 0 replies; 2+ messages in thread
From: Burton, Ross @ 2014-09-15 14:39 UTC (permalink / raw)
  To: Ed Swarthout; +Cc: OE-core

On 15 September 2014 06:10, Ed Swarthout <ed.swarthout@hdebug.com> wrote:
> It looks like udev ptest is the culprit:
>
> /f/deb/home/yocto/yocto/build2014/tmp/sysroots/qemuppc/usr/lib/udev/ptest/test/sys/block/loop0/subsystem/loop0/subsystem:
>   total used in directory 8 available 55515512
>   drwxr-xr-x  2 ed ed0 4096 Aug 24 10:51 .
>   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop0 ->
> ../../devices/virtual/block/loop0
>   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop1 ->
> ../../devices/virtual/block/loop1
>   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop2 ->
> ../../devices/virtual/block/loop2
>   lrwxrwxrwx  1 ed ed0   33 Aug 24 10:51 loop3 ->
> ../../devices/virtual/block/loop3
>
> Does it have to leave these there after it completes the test?

No, it should clean up.  This would be run-ptest in the systemd
recipe, can you submit a tested patch?

Ross


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

end of thread, other threads:[~2014-09-15 14:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-09-15  5:10 udev ptest leaves symlink loops in target sysroots Ed Swarthout
2014-09-15 14:39 ` Burton, Ross

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox