Skip to content

trinity

369 threads 1,158 messages Latest

About Archive
Archive
lore.kernel.org/trinity
  1. PSA: this list has moved to new vger infra (no action required) DISCUSSION Konstantin Ryabitsev 0 replies
  2. Trinity 1.8 DISCUSSION Dave Jones 0 replies
  3. Trinity release soon. DISCUSSION Dave Jones 0 replies
  4. test processes are not all killed DISCUSSION Dai Xiang 7 replies
  5. trinity: execve() returns 0? DISCUSSION Vegard Nossum 1 reply
  6. Trinity 1.7 DISCUSSION Dave Jones 1 reply
  7. invalid open call: O_CREAT or O_TMPFILE without mode BUG Andersen, John 2 replies
  8. child processes stall forever and don't get killed bug Jan Stancek 4 replies
  9. Randomly reopening file descriptors DISCUSSION Vegard Nossum 1 reply
  10. What's the suggestion to do trinity test? DISCUSSION Li jinyue 0 replies
  11. cleanup_net()/net_mutex hung tasks + kobject release debugging DISCUSSION Vegard Nossum lkml 2 replies
  12. Efficient unit test and fuzz tools for kernel/libc porting RFD Zhangjian (Bamvor) linux-arch lkml 7 replies
  13. HEAD of trinity broken on xc86 DISCUSSION Toralf Förster 2 replies
  14. compile error within a 32 bit KVM DISCUSSION Toralf Förster 1 reply
  15. 32bit compile error w/ v1.6-115-g4a302e2 DISCUSSION Toralf Förster 0 replies
  16. nouveau: iowrite32 oops & warning at drivers/gpu/drm/nouveau/nouveau_fence.c:198 DISCUSSION Tommi Rantala dri-devel lkml nouveau 2 replies
  17. "invalid open call: O_CREAT or O_TMPFILE without mode" errors DISCUSSION Vinson Lee 2 replies
  18. x86; *** Error in `trinity': free(): invalid pointer: 0xb6ffe000 *** DISCUSSION Toralf Förster 0 replies
  19. git issue DISCUSSION Toralf Förster 2 replies
  20. intel_sprite_get_colorkey oops DISCUSSION Tommi Rantala dri-devel intel-gfx 0 replies
  21. Trinity v1.5 released. DISCUSSION Dave Jones lkml 0 replies
  22. BUG!: unreachable! BUG!: [29809] generate-args.c:fill_arg:360 DISCUSSION Toralf Förster 0 replies
  23. *** Error in `trinity': free(): invalid pointer: 0xb755c014 *** DISCUSSION Toralf Förster 1 reply
  24. Fix Penguin Penalty 17th October2014 ( mail-archive.com ) DISCUSSION [email protected] 0 replies
  25. trinity doesn't exit after its finished DISCUSSION Toralf Förster linux-um 3 replies
  26. How to read and analysis trinity log file? DISCUSSION [email protected] 0 replies
  27. How to read and analysis trinity log file? DISCUSSION [email protected] 0 replies
  28. BUG!: unreachable! DISCUSSION Toralf Förster 1 reply
  29. Error in `trinity': free(): invalid next size (normal): 0x08683438 *** DISCUSSION Toralf Förster 1 reply
  30. hang in creating the trinity-testfileX DISCUSSION Toralf Förster 3 replies
  31. f2fs get_dnode_of_data oops DISCUSSION Tommi Rantala linux-f2fs-devel lkml 8 replies
  32. endless loop open child logfiles DISCUSSION Toralf Förster 1 reply
  33. compile error of trinity related to an outdated gcc ? DISCUSSION Toralf Förster 1 reply
  34. drm_ioctl & WARNING at arch/x86/mm/ioremap.c:98 DISCUSSION Tommi Rantala dri-devel lkml 0 replies
  35. drm_mode_create_dumb_ioctl: divide error DISCUSSION Tommi Rantala dri-devel lkml 3 replies
  36. /proc/asound/card0/oss_mixer stack corruption DISCUSSION Tommi Rantala alsa-devel lkml 2 replies
  37. <timed out> child0:1694 Toralf Förster 3 replies
  38. trinity seems not to reap all childs DISCUSSION Toralf Förster linux-um 3 replies
  39. trinity cores in watchdog while syslog'ing DISCUSSION Toralf Förster 3 replies
  40. execve returned an undocumented return value (28:No space left on device) child0:1655 Toralf Förster 0 replies
  41. compile error wrt VERSION DISCUSSION Toralf Förster 3 replies
  42. *** Error in `trinity': double free or corruption (!prev): 0x08208e78 *** DISCUSSION Toralf Förster 5 replies
  43. breakage on master. DISCUSSION Dave Jones 1 reply
  44. Trinity 1.4 tarball release. DISCUSSION Dave Jones 9 replies
  45. FYI: git tree moved. DISCUSSION Dave Jones 0 replies
  46. shouldn't the Makefile be adjusted after the rename of sockets.c to fd-sockets.c ? DISCUSSION Toralf Förster 1 reply
  47. GCC 4.9 build error child.c:274:14: error: variable 'lastop' might be clobbered by 'longjmp' or 'vfork' [-Werror=clobbered] DISCUSSION Vinson Lee 1 reply
  48. timer: lockup in run_timer_softirq() DISCUSSION Sasha Levin lkml 16 replies
  49. build error with latest gir tree at a 32 bit Linux DISCUSSION Toralf Förster 2 replies
  50. syscall mremap can't be tested at a UML w/ fuzzy tool trinity uml-devel info Toralf Förster linux-um 2 replies
Page 1 of 3 –