From: hujianyang <hujianyang@huawei.com>
To: Paul Moore <pmoore@redhat.com>
Cc: rgb@redhat.com, linux-audit@redhat.com, jlayton@redhat.com
Subject: Re: [RFC PATCH] audit: correctly record file names with different path name types
Date: Thu, 4 Dec 2014 10:04:00 +0800 [thread overview]
Message-ID: <547FC110.3050703@huawei.com> (raw)
In-Reply-To: <3214700.P9gl05RaQR@sifl>
On 2014/12/4 5:27, Paul Moore wrote:
>
> I setup my system using your configuration and the system booted and ran the
> regression test described in the patch description without problem. I know of
> at least one other person that has tested this patch without problem as well.
>
OK~
>
> I know that many embedded systems include several kernel patches that deviate
> from the upstream sources (device drivers, etc.), is that the case with your
> system?
>
I'm not sure, probably not.
>
> I did test your configuration, without problem. I suspect there is some sort
> of conflict between the patch and one of the kernel patches in your system.
> Is there any chance you can debug the problem you saw?
>
We have a plan to upgrade kernel version from linux 3.10 to linux 3.18.
My colleagues are about to testing your patch with new kernel next week.
So maybe we can find the cause of the panic in my environment in a few
days.
> I'm going to remove the CC:stable from the patch description to be safe, but
> as of right now I think it is reasonable to include the patch in the audit
> next branch.
>
Go ahead~
I will inform you if we fix the panic in my environment as soon as
possible.
Thanks.
Hu
prev parent reply other threads:[~2014-12-04 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 21:27 [RFC PATCH] audit: correctly record file names with different path name types Paul Moore
2014-12-01 21:48 ` Richard Guy Briggs
2014-12-02 7:12 ` hujianyang
2014-12-02 7:31 ` hujianyang
2014-12-02 16:02 ` Paul Moore
2014-12-03 1:54 ` hujianyang
2014-12-03 21:27 ` Paul Moore
2014-12-04 2:04 ` hujianyang [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=547FC110.3050703@huawei.com \
--to=hujianyang@huawei.com \
--cc=jlayton@redhat.com \
--cc=linux-audit@redhat.com \
--cc=pmoore@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 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.