[systemd-devel] log_assert_failed_realm: systemd journal related crash

[Amit anand]

Hi systemd-devel team,

We are getting below crash in our CI environment with systemd v244-stable,
so could you please confirm whether the PR:
https://github.com/systemd/systemd/pull/15557

will fix it? If yes then I will send back port of these PR to v244-stable
as well and if not then could you please help to understand what can be
cause of this?:
(gdb) bt full
#0 __GI_abort () at abort.c:107
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {
18446744073709551615 }}, sa_flags = 0, sa_restorer = 0x0}
sigs = {__val = {32, 0 }}
#1

0x007f87d2900c in log_assert_failed_realm (realm=realm@entry
=LOG_REALM_SYSTEMD,
text=text@entry=0x7f87d41f30 "p > 0",
file=file@entry=0x7f87d41e1f "src/journal/journal-file.c", line=line@entry
=2442,
func=func@entry=0x7f87d42fe0 <*PRETTY_FUNCTION*.13000> "test_object_seqnum")
at ../git/src/basic/log.c:809
No locals.
#2

0x007f87d0e5e8 in test_object_seqnum (f=0x217c, p=0, needle=8572)
at ../git/src/journal/journal-file.c:2442
o =
r =
*PRETTY_FUNCTION* = "test_object_seqnum"
#3

test_object_seqnum (f=f@entry=0x7f78012030, p=p@entry=0, needle=needle@entry
=8572)
at ../git/src/journal/journal-file.c:2437
o = 0x7f8524a0a8
r =
*PRETTY_FUNCTION* = "test_object_seqnum"
#4

0x007f87d0fa84 in generic_array_bisect_plus_one (idx=0x0,
offset=0x7f8524a210, ret=0x0,
direction=DIRECTION_DOWN, test_object=0x7f87d0e528 ,
needle=8572, n=1,
first=0, extra=0, f=0x7f78012030) at ../git/src/journal/journal-file.c:2376
r =
step_back =
o = 0x173318
r =
--Type for more, q to quit, c to continue without paging--
step_back =
o =
*PRETTY_FUNCTION* = "generic_array_bisect_plus_one"
#5

generic_array_bisect_plus_one (f=0x7f78012030, extra=0, first=0, n=1,
needle=8572,
test_object=0x7f87d0e528 , direction=DIRECTION_DOWN,
ret=0x0,
offset=0x7f8524a210, idx=0x0) at ../git/src/journal/journal-file.c:2352
r =
o =
*PRETTY_FUNCTION* = "generic_array_bisect_plus_one"
#6

0x007f87d10f84 in journal_file_move_to_entry_by_seqnum_for_data
(f=f@entry=0x7f78012030,
data_offset=, seqnum=8572, direction=direction@entry=DIRECTION_DOWN,
ret=ret@entry=0x0, offset=offset@entry=0x7f8524a210) at
../git/src/basic/sparse-endian.h:83
d = 0x7f77a0cce8

Re: [systemd-devel] [EXT] Initialization of "vbuf" in function "token_match_attr"

[Amit anand]

Hi,

On Tue, Sep 8, 2020 at 6:23 PM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:

> Hi!
>
> vbuf is initialized: It has some address on the stack, so "if (value !=
> vbuf)" is comparing adresses, if I got it right...
>
vbuf having some address on stack and "if(value!=vbuf)" is comparing
addresses doesn't necessarily implies that vbuf is initialized.
I am still not clear about where vbuf is initialized.
Also, expecting some information regarding my queries in below mail.

Thanks,
Amit

>
> >>> Amit anand  schrieb am 08.09.2020 um 13:56 in
> Nachricht
> :
> > Hi systemd-devel team,
> >
> > I am trying to understand where "vbuf" is initialized in function
> > "token_match_attr()" in file udev-rules.c
> >
> > Below code snippet :
> > static bool* token_match_attr*(UdevRuleToken *token, sd_device *dev,
> > UdevEvent *event) {
> >  *char* nbuf[UTIL_NAME_SIZE], *vbuf*[UTIL_NAME_SIZE]; // Here, vbuf
> is
> > defined, however not initialized.
> > *const char* *name, **value;*// Here, value is declared to be of
> > type const char *, however, not initialized.
> > ...
> > ... // some code
> > ...
> > switch (token->attr_subst_type) {   // *Event 1* : This evaluates to
> > SUBST_TYPE_PLAIN
> > ...
> > case *SUBST_TYPE_PLAIN*:   if (sd_device_get_sysattr_value(dev, name,
> > ) < 0)   // *Event 2* :The if condition evaluates to false.
> >  return false;
> >  break;
> > ...// some code
> > ...
> > }
> >
> > if (token->attr_match_remove_trailing_whitespace) {  //
> *Event
> > 4*: If condition evaluates to true
> > if (value != vbuf) {  //  *Event 5* : vbuf and value
> > are both declared but not initialized. Comparison is done without
> > initializing "vbuf" and "value".
> > strscpy(vbuf, sizeof(vbuf), value);
> > value = vbuf;
> > } // End of if.
> >
> > delete_trailing_chars(vbuf, NULL); // *Event 6*:
> > trying to delete trailing chars from "vbuf" which is not initialzed. ??
> > } // End of outer if.
> > ... // some code
> > } /End of function : *token_match_attr()*
> >
> > Below are my queries :
> > 1. *Event 5 *above, we are comparing two resources ("value" and "vbuf")
> > even before initializing them.
> > Are we doing this comparision to do decision making based on whether
> > the pointer type variable "value" is pointing to "vbuf" or not.
> > *Query*: Kindly confirm whether my understanding is correct.
> >
> > 2. *Event 6* above, delete_trailing_chars(vbuf, NULL) is called outside
> *if
> > (value != vbuf).*
> > This implies there may occur a situation where:
> >   step 1 ) *if (value != vbuf) *condition fails  --> step 2 )
> > *vbuf* is not initialzed inside the *if(value != vbuf)  *--> step 3 )
> > delete_trailing_chars(*vbuf*, NULL).
> > Here, delete_trailing_chars() called for "*vbuf*" which is not
> necessarily
> > initiazlied.
> > *Query*: Kindly let me know if my understanding is correct or I am
> missing
> > something.
> >
> > Thanks,
> > Amit
>
>
>
>
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Initialization of "vbuf" in function "token_match_attr"

[Amit anand]

Hi systemd-devel team,

I am trying to understand where "vbuf" is initialized in function
"token_match_attr()" in file udev-rules.c

Below code snippet :
static bool* token_match_attr*(UdevRuleToken *token, sd_device *dev,
UdevEvent *event) {
 *char* nbuf[UTIL_NAME_SIZE], *vbuf*[UTIL_NAME_SIZE]; // Here, vbuf is
defined, however not initialized.
*const char* *name, **value;*// Here, value is declared to be of
type const char *, however, not initialized.
...
... // some code
...
switch (token->attr_subst_type) {   // *Event 1* : This evaluates to
SUBST_TYPE_PLAIN
...
case *SUBST_TYPE_PLAIN*:   if (sd_device_get_sysattr_value(dev, name,
) < 0)   // *Event 2* :The if condition evaluates to false.
 return false;
 break;
...// some code
...
}

if (token->attr_match_remove_trailing_whitespace) {  // *Event
4*: If condition evaluates to true
if (value != vbuf) {  //  *Event 5* : vbuf and value
are both declared but not initialized. Comparison is done without
initializing "vbuf" and "value".
strscpy(vbuf, sizeof(vbuf), value);
value = vbuf;
} // End of if.

delete_trailing_chars(vbuf, NULL); // *Event 6*:
trying to delete trailing chars from "vbuf" which is not initialzed. ??
} // End of outer if.
... // some code
} /End of function : *token_match_attr()*

Below are my queries :
1. *Event 5 *above, we are comparing two resources ("value" and "vbuf")
even before initializing them.
Are we doing this comparision to do decision making based on whether
the pointer type variable "value" is pointing to "vbuf" or not.
*Query*: Kindly confirm whether my understanding is correct.

2. *Event 6* above, delete_trailing_chars(vbuf, NULL) is called outside  *if
(value != vbuf).*
This implies there may occur a situation where:
  step 1 ) *if (value != vbuf) *condition fails  --> step 2 )
*vbuf* is not initialzed inside the *if(value != vbuf)  *--> step 3 )
delete_trailing_chars(*vbuf*, NULL).
Here, delete_trailing_chars() called for "*vbuf*" which is not necessarily
initiazlied.
*Query*: Kindly let me know if my understanding is correct or I am missing
something.

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

Re: [systemd-devel] Upstreaming systemd patch

[Amit anand]

Hi,

Not able to create pull request to systemd, permission denied to my github
user credentials.

I git cloned https://github.com/systemd/systemd

While creating pull request,
git push --set-upstream origin 
1. Entered github username
2. Entered github passwd
getting below error message for my github username.
remote: Permission to systemd/systemd.git denied to 
fatal : unable to access 'https://github.com/systemd/systemd.git/': The
requested URL returned error: 403

When tried to connect IRC channel irc://irc.freenode.org/systemd , it is
giving error message "irc.freenode.org: Terminated".

Please let me know to whom I need to connect with for getting pull request
creation permission to systemd project.

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

[systemd-devel] Upstreaming systemd patch

[Amit anand]

Hi systemd-devel group,


I need to upstream systemd git patch for fixing systemd static code
analysis warnings.

Can you please suggest me the correct mailgroup to send the git patch or
relevant web url which have information to upstream git patch.

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

Re: [systemd-devel] Not able to get valgrind profiling output after starting systemd-udevd.service through valgrind.

[Amit anand]

Hi,

Tried to run debug-symbol enabled systemd-udevd through valgrind.
root@[xxx]:/var/opt# vi  /etc/systemd/system/.../systemd-udevd.service
ExecStart=/usr/bin/valgrind --tool=memcheck
/lib/systemd/.debug/systemd-udevd  // Modified to run debug-symbol enabled
systemd.udevd binary through valgrind.
root@[xxx]:/var/opt# systemctl daemon-reload

Not able to run debug-symbol enabled systemd-udevd through valgrind.
Below error message:
root@[xxx]:/var/opt# systemctl restart systemd-udevd
Job for systemd-udevd.service failed because the control process exited
with error code.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for
details

systemctl status -n1000 systemd-udevd.service
[[0;1;31m●[[0m systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; enabled;
vendor preset: enabled)
   Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2020-04-21
16:27:16 UTC; 40s ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
  Process: 4252 ExecStart=/usr/bin/valgrind --tool=memcheck
/lib/systemd/.debug/systemd-udevd [[0;1;31m(code=exited,
status=1/FAILURE)[[0m
 Main PID: 4252 (code=exited, status=1/FAILURE)

Apr 21 16:27:16 [xxx] valgrind[4252]: valgrind: m_ume.c: can't open
interpreter
Apr 21 16:27:16 [xxx] systemd[1]:
[[0;1;39m[[0;1;31m[[0;1;39msystemd-udevd.service: Failed with result
'exit-code'.[[0m
Apr 21 16:27:16 [xxx] systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to
start udev Kernel Device Manager.[[0m

 Kindly let me know if anything missed.

Regards,
Amit

On Thu, Apr 16, 2020 at 7:26 PM Lennart Poettering 
wrote:

> On Di, 14.04.20 20:00, Amit anand (amit.ta...@gmail.com) wrote:
>
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012BD1: ???
> > (in /lib/ld-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
> > _dl_catch_exception (in /lib/libc-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012789: ???
> > (in /lib/ld-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC2DC: ???
> > (in /lib/libc-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
> > _dl_catch_exception (in /lib/libc-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCCFE:
> > _dl_catch_error (in /lib/libc-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC3A6: ???
> > (in /lib/libc-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC436:
> > __libc_dlopen_mode (in /lib/libc-2.27.so)
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==  Address 0x650b1c0 is
> > 16 bytes after a block of size 32 in arena "client"
> > Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==
>
> To be truly useful you need to enable debug symbols in your builds, so
> that valgrind can show you something for useful than pointer values.
>
> Lennart
>
> --
> Lennart Poettering, Berlin
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Not able to get valgrind profiling output after starting systemd-udevd.service through valgrind.

[Amit anand]

Hi,
I am trying to run systemd-udevd.service through valgrind for
debugging some memory corruption issue in file
https://github.com/systemd/systemd/blob//src/basic/hashmap.c
file..

OS info :  64 bit Ubuntu OS. This is run
as guest vm.
RAM memory /swap size : 4GB RAM and 3 GB SWAP space.
systemd version   : systemd v237.

The command uname -a gives below result.
Linux [xxx] 4.14.147-yocto-standard #1 SMP PREEMPT Thu Jan 30 18:52:38
UTC 2020 x86_64 GNU/Linux
note : [xxx] is masked text.

Followed steps mentioned in URL
"https://lists.freedesktop.org/archives/systemd-devel/2020-April/044367.html;
to start systemd-udevd.service in valgrind.


Could see few lines of valgrind output with "systemctl status
systemd-udev.service" command

Below information displayed on console.

Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012BD1: ???
(in /lib/ld-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
_dl_catch_exception (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012789: ???
(in /lib/ld-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC2DC: ???
(in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
_dl_catch_exception (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCCFE:
_dl_catch_error (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC3A6: ???
(in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC436:
__libc_dlopen_mode (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==  Address 0x650b1c0 is
16 bytes after a block of size 32 in arena "client"
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==

Note : [xxx] is masked text.

Initial few lines (7-8 lines) of valgrind profiling output is available.

Can you please let me know if there is any other way or tool available
to identify how memory allocation and release done in
systemd-udevd.service.


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

Re: [systemd-devel] OS shutting down after starting systemd-udevd.service through valgrind

[Amit anand]

Hi,

OS shutdown issue resolved after disabling recmanager and crashhander services.

Thanks,

On 4/3/20, Amit anand  wrote:
> Hi,
> I am trying to run systemd-udevd.service through valgrind for debugging
> some memory corruption issue.
>
> OS info :  64 bit Ubuntu OS. This is run as
> guest vm.
> RAM memory /swap size : 4GB RAM and 3 GB SWAP space.
> systemd version   : systemd v237.
>
> The command uname -a gives below result.
> Linux [xxx] 4.14.147-yocto-standard #1 SMP PREEMPT Thu Jan 30 18:52:38 UTC
> 2020 x86_64 GNU/Linux
> note : [xxx] is masked text.
>
> Referred to link
> *https://lists.freedesktop.org/archives/systemd-devel/2015-April/030086.html
> <https://lists.freedesktop.org/archives/systemd-devel/2015-April/030086.html>*
> .
> Followed below steps to run systemd-udev.service through valgrind.
>
> *step 1* :
> On terminal, command "systemctl edit --full systemd-udev.service"
>
> Prefixed it's ExecStart= parameter with an invocation of valgrind as below,
> ExecStart=/usr/bin/valgrind --tool=memcheck /lib/systemd/systemd-udevd
>
> *Step 2* :
> On terminal, command "systemctl daemon-reload"
>
> Step 3 :
> On terminal, command "systemctl restart systemd-udevd"
>
> Step 4 :
> On terminal, command ps command gave below result for udevd.
> [[0;1;32m●[[0m systemd-udevd.service - udev Kernel Device Manager
>Loaded: loaded (/etc/systemd/system/systemd-udevd.service; enabled;
> vendor preset: enabled)
>Active: [[0;1;32mactive (running)[[0m since Fri 2020-04-03 14:40:41 UTC;
> 9s ago
>  Docs: man:systemd-udevd.service(8)
>man:udev(7)
>  Main PID: 13179 (memcheck-amd64-)
>Status: "Processing with 16 children at max"
>Memory: 42.6M
>CGroup: /system.slice/systemd-udevd.service
>└─13179 /usr/bin/valgrind --tool=memcheck
> /lib/systemd/systemd-udevd
>
>
> Step 5 : Could see few lines of valgrind output with "systemctl status
> systemd-udev.service" command
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012BD1: ??? (in
> /lib/ld-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
> _dl_catch_exception (in /lib/libc-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012789: ??? (in
> /lib/ld-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC2DC: ??? (in
> /lib/libc-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
> _dl_catch_exception (in /lib/libc-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCCFE:
> _dl_catch_error (in /lib/libc-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC3A6: ??? (in
> /lib/libc-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC436:
> __libc_dlopen_mode (in /lib/libc-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==  Address 0x650b1c0 is 16
> bytes after a block of size 32 in arena "client"
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==
>
> Note : [xxx] is masked text.
>
> However, guest vm (Ubuntu OS) shut down within 2 minutes of restarting
> systemd-udevd service.
> Attempt to reboot the guest vm ( Ubuntu OS) failed.
>
> Can you please guide/suggest how to prevent the Ubuntu OS from shutting
> down after restarting systemd-udevd.service with valgrind.
>
> Thanks,
> Amit
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] OS shutting down after starting systemd-udevd.service through valgrind

[Amit anand]

Hi,
I am trying to run systemd-udevd.service through valgrind for debugging
some memory corruption issue.

OS info :  64 bit Ubuntu OS. This is run as
guest vm.
RAM memory /swap size : 4GB RAM and 3 GB SWAP space.
systemd version   : systemd v237.

The command uname -a gives below result.
Linux [xxx] 4.14.147-yocto-standard #1 SMP PREEMPT Thu Jan 30 18:52:38 UTC
2020 x86_64 GNU/Linux
note : [xxx] is masked text.

Referred to link
*https://lists.freedesktop.org/archives/systemd-devel/2015-April/030086.html
*
.
Followed below steps to run systemd-udev.service through valgrind.

*step 1* :
On terminal, command "systemctl edit --full systemd-udev.service"

Prefixed it's ExecStart= parameter with an invocation of valgrind as below,
ExecStart=/usr/bin/valgrind --tool=memcheck /lib/systemd/systemd-udevd

*Step 2* :
On terminal, command "systemctl daemon-reload"

Step 3 :
On terminal, command "systemctl restart systemd-udevd"

Step 4 :
On terminal, command ps command gave below result for udevd.
[[0;1;32m●[[0m systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/etc/systemd/system/systemd-udevd.service; enabled;
vendor preset: enabled)
   Active: [[0;1;32mactive (running)[[0m since Fri 2020-04-03 14:40:41 UTC;
9s ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
 Main PID: 13179 (memcheck-amd64-)
   Status: "Processing with 16 children at max"
   Memory: 42.6M
   CGroup: /system.slice/systemd-udevd.service
   └─13179 /usr/bin/valgrind --tool=memcheck
/lib/systemd/systemd-udevd


Step 5 : Could see few lines of valgrind output with "systemctl status
systemd-udev.service" command
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012BD1: ??? (in
/lib/ld-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
_dl_catch_exception (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012789: ??? (in
/lib/ld-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC2DC: ??? (in
/lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
_dl_catch_exception (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCCFE:
_dl_catch_error (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC3A6: ??? (in
/lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFC436:
__libc_dlopen_mode (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==  Address 0x650b1c0 is 16
bytes after a block of size 32 in arena "client"
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==

Note : [xxx] is masked text.

However, guest vm (Ubuntu OS) shut down within 2 minutes of restarting
systemd-udevd service.
Attempt to reboot the guest vm ( Ubuntu OS) failed.

Can you please guide/suggest how to prevent the Ubuntu OS from shutting
down after restarting systemd-udevd.service with valgrind.

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