From: Paul Moore <paul@paul-moore.com>
To: kasseyli@outlook.com
Cc: linux-audit@redhat.com
Subject: Re: 4.9 kernel panic in netlink unicast because audit replace passing audit sock as NULL
Date: Sat, 13 Oct 2018 11:57:09 -0400 [thread overview]
Message-ID: <CAHC9VhQnKdvYHn7sQANieOk4KwPEX3GRkWLdAaPF7B6Od70ZRA@mail.gmail.com> (raw)
In-Reply-To: <SG2PR04MB3350813F1DF4E10641116FD5CFE20@SG2PR04MB3350.apcprd04.prod.outlook.com>
On Fri, Oct 12, 2018 at 3:33 AM Kassey Li <kasseyli@outlook.com> wrote:
> hi, Paul:
>
> it is hard to running on upstream kernel on my hardware.
> I checked the kernel log that we can see that we are trying to send the sock to task 20802, but it was killed already.
> is there any suggest that we can pick up some patches to backport to 4.9 to try ?
There have been numerous patches which could be applicable to your
problem, starting in v4.10 through v4.15. Since this is an old kernel
from an upstream community perspective I would suggest reaching out to
your Linux distribution's support channels to see if they can help
you. If that is not an option, you can see all of the audit patches
from the audit team in the audit kernel repo broken down by release at
the following location:
* git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
* https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
... patches for Linux vX.Y can be found in branches stable-X.Y.
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2018-10-13 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 2:43 4.9 kernel panic in netlink unicast because audit replace passing audit sock as NULL Kassey Li
2018-10-12 4:15 ` Paul Moore
2018-10-12 7:33 ` Kassey Li
2018-10-13 15:57 ` Paul Moore [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=CAHC9VhQnKdvYHn7sQANieOk4KwPEX3GRkWLdAaPF7B6Od70ZRA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=kasseyli@outlook.com \
--cc=linux-audit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.