From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: audit: update to 3.0
Date: Mon, 15 Feb 2021 21:46:10 +0100 [thread overview]
Message-ID: <20210215204610.OEmK_40KTTfR-zzDuaX_jNxtRAcksrMWtJ8gOUpPt9Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28447@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/28447#issuecomment-779440381
Comment:
```
$ lib/test/lookup_test
Testing i386_table...
Testing ppc_table...
Testing s390_table...
Testing s390x_table...
Testing x86_64_table...
Testing actiontab...
Testing errtab...
Testing fieldtab...
Unexpected match `A1'
```
the test failing is on [line 281](https://github.com/linux-audit/audit-userspace/blob/master/lib/test/lookup_test.c#L281) which calls TEST_S2I which contains this part:
```c
/* Blindly assuming this will not generate a \
meaningful identifier. */ \
gen_id(buf); \
if (S2I(buf) != (ERR_VALUE)) { \
fprintf(stderr, \
"Unexpected match `%s'\n", \
buf); \
abort(); \
} \
```
ERR_VALUE = -1 and S2I(buf) = 201, so it seems to me like it actually generated a valid identifier, but I am a bit lost.
next prev parent reply other threads:[~2021-02-15 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 19:35 [PR PATCH] " paper42
2021-02-03 19:52 ` ericonr
2021-02-10 1:13 ` ericonr
2021-02-10 1:13 ` ericonr
2021-02-10 10:01 ` paper42
2021-02-10 13:33 ` ericonr
2021-02-10 15:21 ` paper42
2021-02-15 17:19 ` ericonr
2021-02-15 17:21 ` ericonr
2021-02-15 20:46 ` paper42 [this message]
2021-02-15 20:46 ` [PR PATCH] [Updated] " paper42
2021-04-03 3:31 ` ericonr
2021-04-03 3:32 ` [PR PATCH] [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=20210215204610.OEmK_40KTTfR-zzDuaX_jNxtRAcksrMWtJ8gOUpPt9Y@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).