From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Evgeny Vereshchagin <evvers@ya.ru>,
SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH 1/2] ci: turn on CIFuzz
Date: Tue, 13 Jul 2021 21:57:57 +0200 [thread overview]
Message-ID: <CAJfZ7=mxOsGMvHotZYSwYAW6pQLkwZ2-CyeuAEUzBaAAUztbPQ@mail.gmail.com> (raw)
In-Reply-To: <CAJfZ7=m=8t9MQ1gSHE9_9D8aki-mUrWtnYTBVreeuGDwaRK_hA@mail.gmail.com>
On Mon, Jul 12, 2021 at 9:31 AM Nicolas Iooss <nicolas.iooss@m4x.org> wrote:
>
> On Sat, Jul 10, 2021 at 2:11 PM Evgeny Vereshchagin <evvers@ya.ru> wrote:
> >
> > Now that almost all the bugs reported by OSS-Fuzz have been
> > fixed libsepol/cil should be stable enough to get CIFuzz working
> > more or less reliably. It should help to catch regressions/new bugs
> > faster.
> >
> > https://google.github.io/oss-fuzz/getting-started/continuous-integration/
> >
> > The patch was tested on GitHub in https://github.com/SELinuxProject/selinux/pull/285
> > The CIFuzz job can be found at https://github.com/SELinuxProject/selinux/actions/runs/1017865690
> >
> > Signed-off-by: Evgeny Vereshchagin <evvers@ya.ru>
>
> For both patches:
>
> Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>
>
> If nobody else has comments, I will apply them tomorrow.
> Thanks!
> Nicolas
Merged.
Thanks!
Nicolas
> > ---
> > .github/workflows/cifuzz.yml | 39 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 39 insertions(+)
> > create mode 100644 .github/workflows/cifuzz.yml
> >
> > diff --git a/.github/workflows/cifuzz.yml b/.github/workflows/cifuzz.yml
> > new file mode 100644
> > index 00000000..5c2233a2
> > --- /dev/null
> > +++ b/.github/workflows/cifuzz.yml
> > @@ -0,0 +1,39 @@
> > +---
> > +name: CIFuzz
> > +on:
> > + push:
> > + branches:
> > + - master
> > + pull_request:
> > + branches:
> > + - master
> > +jobs:
> > + Fuzzing:
> > + runs-on: ubuntu-latest
> > + if: github.repository == 'SELinuxProject/selinux'
> > + strategy:
> > + fail-fast: false
> > + matrix:
> > + sanitizer: [address, undefined, memory]
> > + steps:
> > + - name: Build Fuzzers (${{ matrix.sanitizer }})
> > + id: build
> > + uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
> > + with:
> > + oss-fuzz-project-name: 'selinux'
> > + dry-run: false
> > + allowed-broken-targets-percentage: 0
> > + sanitizer: ${{ matrix.sanitizer }}
> > + - name: Run Fuzzers (${{ matrix.sanitizer }})
> > + uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
> > + with:
> > + oss-fuzz-project-name: 'selinux'
> > + fuzz-seconds: 180
> > + dry-run: false
> > + sanitizer: ${{ matrix.sanitizer }}
> > + - name: Upload Crash
> > + uses: actions/upload-artifact@v1
> > + if: failure() && steps.build.outcome == 'success'
> > + with:
> > + name: ${{ matrix.sanitizer }}-artifacts
> > + path: ./out/artifacts
> > --
> > 2.31.1
> >
prev parent reply other threads:[~2021-07-13 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 12:03 [PATCH 1/2] ci: turn on CIFuzz Evgeny Vereshchagin
2021-07-10 12:03 ` [PATCH 2/2] README: add OSS-Fuzz/CIFuzz badges Evgeny Vereshchagin
2021-07-12 7:31 ` [PATCH 1/2] ci: turn on CIFuzz Nicolas Iooss
2021-07-13 19:57 ` Nicolas Iooss [this message]
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='CAJfZ7=mxOsGMvHotZYSwYAW6pQLkwZ2-CyeuAEUzBaAAUztbPQ@mail.gmail.com' \
--to=nicolas.iooss@m4x.org \
--cc=evvers@ya.ru \
--cc=selinux@vger.kernel.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).