Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 1/6] audit: bump to version 2.6
Date: Wed, 6 Jul 2016 22:43:53 +0200	[thread overview]
Message-ID: <20160706204353.GD3763@free.fr> (raw)
In-Reply-To: <CAFSsvmrb56wuAp5mo5r6e-ZrNK2SF=wFs_3OW_WtdezqGVrCqw@mail.gmail.com>

Adam, All,

On 2016-07-06 10:42 -0400, Adam Duskett spake thusly:
> I think this is a bug in Audit actually.
> 
> Audit 2.6.x checks for AUDIT_FEATURE_VERSION to be defined in
> include/linux/audit.h (this define was introduced in kernel version
> 3.13) and then blindly assumes that struct audit_status has
> feature_bitmap.
> However this looks like a problem as feature_bitmap wasn't introduced
> until kernel 3.19, even though the requirements for audit state >
> 2.6.30 (http://people.redhat.com/sgrubb/audit/)
> 
> This causes a compile error when attempting to compile audit 2.6.x
> against kernel headers younger than 3.19.

Thanks for investigating and explaining! :-)

> For the mean time i could add a conditional to require header versions
> > 3.19, although I am going to submit a bug report to the audit team
> as well.

I was gonna reply with a "depend on linux >= 3.19" but Thomas already
sent a patch to fix it.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-07-06 20:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26 22:39 [Buildroot] [PATCH v6 0/6] *** Update selinux libraries *** Adam Duskett
2016-06-26 22:39 ` [Buildroot] [PATCH v6 1/6] audit: bump to version 2.6 Adam Duskett
2016-06-29 19:42   ` Yann E. MORIN
2016-07-01  9:08   ` Thomas Petazzoni
2016-07-05 17:16   ` Yann E. MORIN
2016-07-06 13:47     ` Adam Duskett
2016-07-06 14:42       ` Adam Duskett
2016-07-06 20:43         ` Yann E. MORIN [this message]
2016-06-26 22:39 ` [Buildroot] [PATCH v6 2/6] libsemanage: bump to version 2.5 Adam Duskett
2016-06-29 20:32   ` Yann E. MORIN
2016-07-01  9:08   ` Thomas Petazzoni
2016-06-26 22:39 ` [Buildroot] [PATCH v6 3/6] checkpolicy: " Adam Duskett
2016-06-29 20:34   ` Yann E. MORIN
2016-07-01  9:10   ` Thomas Petazzoni
2016-06-26 22:39 ` [Buildroot] [PATCH v6 4/6] libselinux: " Adam Duskett
2016-06-30 22:38   ` Yann E. MORIN
2016-07-01  9:10   ` Thomas Petazzoni
2016-06-26 22:39 ` [Buildroot] [PATCH v6 5/6] libsepol: " Adam Duskett
2016-07-01  9:11   ` Thomas Petazzoni
2016-06-26 22:39 ` [Buildroot] [PATCH v6 6/6] setools: fix build with latest selinux libraries Adam Duskett
2016-07-01  9:11   ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2016-06-26 22:26 [Buildroot] [PATCH 1/6] audit: bump to version 2.6 Adam Duskett
2016-06-26 22:26 ` [Buildroot] [PATCH v6 " Adam Duskett

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=20160706204353.GD3763@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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