From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Apparmor Seg Fault
Date: Sun, 24 Jan 2021 22:57:55 +0100 [thread overview]
Message-ID: <20210124215755.S16yFHRKBGGYYOr_nZJgOAfW2jU4kKcOatq9h603K-w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28127@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/28127#issuecomment-766439271
Comment:
I managed to reproduce this on 5.4 kernel:
```
Core was generated by `aa-status'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 printf_core (f=f@entry=0x0, fmt=fmt@entry=0x0, ap=ap@entry=0x7fff782de018, nl_arg=nl_arg@entry=0x7fff782de060, nl_type=nl_type@entry=0x7fff782de030) at src/stdio/vfprintf.c:454
454 src/stdio/vfprintf.c: No such file or directory.
#0 printf_core (f=f@entry=0x0, fmt=fmt@entry=0x0, ap=ap@entry=0x7fff782de018, nl_arg=nl_arg@entry=0x7fff782de060, nl_type=nl_type@entry=0x7fff782de030) at src/stdio/vfprintf.c:454
#1 0x00007f2d71f482c7 in vfprintf (f=f@entry=0x7fff782de1b0, fmt=0x0, ap=<optimized out>) at src/stdio/vfprintf.c:668
#2 0x00007f2d71f4b0fa in vsnprintf (s=s@entry=0x0, n=n@entry=0, fmt=fmt@entry=0x0, ap=ap@entry=0x7fff782de2c0) at src/stdio/vsnprintf.c:54
#3 0x00007f2d71f45da3 in vasprintf (s=s@entry=0x7fff782de3f0, fmt=0x0, ap=ap@entry=0x7fff782de310) at src/stdio/vasprintf.c:10
#4 0x000056039bf95c7b in _aa_asprintf (strp=strp@entry=0x7fff782de3f0, fmt=<optimized out>) at private.c:180
#5 0x000056039bf9407a in procattr_path (attr=0x56039bf9a57b "current", pid=1) at kernel.c:262
#6 procattr_open (tid=tid@entry=1, attr=attr@entry=0x56039bf9a57b "current", flags=flags@entry=0) at kernel.c:272
#7 0x000056039bf9456e in aa_getprocattr_raw (tid=tid@entry=1, attr=attr@entry=0x56039bf9a57b "current", buf=buf@entry=0x56039bf9fc60 "", len=len@entry=128, mode=mode@entry=0x7fff782de520) at kernel.c:408
#8 0x000056039bf946f6 in aa_getprocattr (mode=<optimized out>, label=<optimized out>, attr=<optimized out>, tid=<optimized out>) at kernel.c:501
#9 aa_getprocattr (tid=1, attr=attr@entry=0x56039bf9a57b "current", label=label@entry=0x7fff782de518, mode=mode@entry=0x7fff782de520) at kernel.c:479
#10 0x000056039bf928b1 in get_processes (profiles=0x56039df5b020, n=58, processes=processes@entry=0x7fff782de5c8, nprocesses=nprocesses@entry=0x7fff782de5b8) at aa_status.c:246
#11 0x000056039bf93531 in detailed_output (json=json@entry=0x0) at aa_status.c:453
#12 0x000056039bf93c31 in cmd_verbose (command=<optimized out>) at aa_status.c:588
#13 0x000056039bf92426 in main (argc=<optimized out>, argv=0x7fff782de6d8) at aa_status.c:660
```
next prev parent reply other threads:[~2021-01-24 21:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 20:41 [ISSUE] " anon-lestat
2021-01-23 22:19 ` ericonr
2021-01-23 22:20 ` ericonr
2021-01-24 0:29 ` paper42
2021-01-24 0:49 ` anon-lestat
2021-01-24 0:50 ` anon-lestat
2021-01-24 1:15 ` [ISSUE] [CLOSED] " anon-lestat
2021-01-24 1:16 ` anon-lestat
2021-01-24 4:48 ` CameronNemo
2021-01-24 11:42 ` anon-lestat
2021-01-24 11:50 ` anon-lestat
2021-01-24 20:00 ` ericonr
2021-01-24 20:16 ` anon-lestat
2021-01-24 20:17 ` ericonr
2021-01-24 20:25 ` ericonr
2021-01-24 20:36 ` anon-lestat
2021-01-24 20:38 ` ericonr
2021-01-24 21:03 ` ericonr
2021-01-24 21:09 ` anon-lestat
2021-01-24 21:16 ` ericonr
2021-01-24 21:20 ` anon-lestat
2021-01-24 21:22 ` anon-lestat
2021-01-24 21:24 ` anon-lestat
2021-01-24 21:32 ` ericonr
2021-01-24 21:52 ` ericonr
2021-01-24 21:54 ` anon-lestat
2021-01-24 21:56 ` ericonr
2021-01-24 21:57 ` anon-lestat
2021-01-24 21:57 ` paper42 [this message]
2021-01-24 22:00 ` ericonr
2021-01-24 22:08 ` paper42
2021-01-24 23:09 ` anon-lestat
2021-01-24 23:18 ` CameronNemo
2021-01-25 1:28 ` ericonr
2021-01-25 1:31 ` anon-lestat
2021-02-04 3:28 ` ericonr
2021-02-04 13:12 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210124215755.S16yFHRKBGGYYOr_nZJgOAfW2jU4kKcOatq9h603K-w@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).