Re: segfault at 968 Error

2016-12-01 Thread VigneshDhanraj G
Thanks, same file consistently it is crashing. On Fri, Dec 2, 2016 at 12:44 PM, wrote: > does it crash reproducable at the same file or is it randomly? > > Am 2. Dezember 2016 07:50:20 MEZ, schrieb VigneshDhanraj G < > vigneshdhanra...@gmail.com>: > >> Any update on this issue.

Re: segfault at 968 Error

2016-12-01 Thread devzero
does it crash reproducable at the same file or is it randomly? Am 2. Dezember 2016 07:50:20 MEZ, schrieb VigneshDhanraj G : >Any update on this issue. > >On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G < >vigneshdhanra...@gmail.com> wrote: > >> Hi Team, >> >> While

Re: segfault at 968 Error

2016-12-01 Thread VigneshDhanraj G
Any update on this issue. On Wed, Nov 30, 2016 at 6:29 PM, VigneshDhanraj G < vigneshdhanra...@gmail.com> wrote: > Hi Team, > > While Running rsync rsync://username@ip:873 , I am getting following > error. > > rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by > peer (104) >

[PATCH v2 1/2] xattrs: Skip security.evm extended attribute

2016-12-01 Thread Stefan Berger
The security.evm extended attribute is fully owned by the Linux kernel and cannot be directly written from userspace. Therefore, we can always skip it. --- xattrs.c | 18 +- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/xattrs.c b/xattrs.c index b105392..3b72e61

[PATCH v2 2/2] xattrs: Properly handle security.ima extended attribute

2016-12-01 Thread Stefan Berger
This patch addresses the proper handling of the security.ima extended attribute in the following two cases: - The security.ima extended attribute is not writeable if its value represents a hash, since hash values are only writeable by the kernel. We therefore ignore errors when security.ima could