From mboxrd@z Thu Jan 1 00:00:00 1970 From: hujianyang Subject: Re: [RFC PATCH] audit: correctly record file names with different path name types Date: Thu, 4 Dec 2014 10:04:00 +0800 Message-ID: <547FC110.3050703@huawei.com> References: <20141201212747.19982.27425.stgit@localhost> <7974163.PYVG5D7BPp@sifl> <547E6D42.1000503@huawei.com> <3214700.P9gl05RaQR@sifl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3214700.P9gl05RaQR@sifl> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Paul Moore Cc: rgb@redhat.com, linux-audit@redhat.com, jlayton@redhat.com List-Id: linux-audit@redhat.com 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