From: Paul Moore <paul@paul-moore.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: bauen1 <j2468h@googlemail.com>,
linux-audit@redhat.com,
Dominick Grift <dominick.grift@defensec.nl>
Subject: Re: null pointer dereference regression in 5.7
Date: Fri, 24 Jul 2020 15:10:18 -0400 [thread overview]
Message-ID: <CAHC9VhTwW07upzC4dFFXM8ozXcD0++dK1FXr8bjv=ZV_FSJGFw@mail.gmail.com> (raw)
In-Reply-To: <20200723125645.mfvuss2m2b6bou3s@madcap2.tricolour.ca>
On Thu, Jul 23, 2020 at 8:57 AM Richard Guy Briggs <rgb@redhat.com> wrote:
> On 2020-07-22 21:01, Paul Moore wrote:
> > Do you have a rough idea as to how long it would take to chase down
> > all the code paths? I'm asking not to rush you, but to figure out if
> > we should revert the patch now to resolve the problem and restore it
> > later once we are confident there are no additional issues lurking.
>
> I figure 2-3 days.
Okay. I think we need to submit a revert for v5.8 and -stable (which
is pretty limited at this point); can you put that together and send
it to the list? It should be trivial, if you can't do it let me know.
> I'm trying to remember the name of the tool to build a function calling
> tree, either up or down. Was it cscope? Or is there something more
> modern? It will have some limitations due to op function pointers.
I'm not sure what you're talking about, I always just walk the code by
hand in my editor with cscope or lxr as tools on the side.
--
paul moore
www.paul-moore.com
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-07-24 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 18:40 null pointer dereference regression in 5.7 bauen1
2020-07-18 18:56 ` Dominick Grift
2020-07-21 22:30 ` Paul Moore
2020-07-21 22:45 ` Paul Moore
2020-07-21 23:09 ` Richard Guy Briggs
2020-07-22 2:01 ` Richard Guy Briggs
2020-07-23 1:01 ` Paul Moore
2020-07-23 12:56 ` Richard Guy Briggs
2020-07-24 19:10 ` Paul Moore [this message]
2020-07-22 19:47 ` Richard Guy Briggs
2020-07-22 20:04 ` Dominick Grift
2020-07-23 12:47 ` Richard Guy Briggs
2020-07-23 12:58 ` Dominick Grift
2020-07-23 13:10 ` bauen1
2020-07-23 20:00 ` Richard Guy Briggs
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='CAHC9VhTwW07upzC4dFFXM8ozXcD0++dK1FXr8bjv=ZV_FSJGFw@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=dominick.grift@defensec.nl \
--cc=j2468h@googlemail.com \
--cc=linux-audit@redhat.com \
--cc=rgb@redhat.com \
/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).