Re: [PATCH v4] Fix missing flags in stat related compatibility syscalls

On Wed, Mar 29, 2017 at 4:47 AM, Dmitry V. Levin wrote: > On Tue, Mar 28, 2017 at 09:26:20AM +0530, Abhishek Tiwari wrote: >> From f6d4386bd952ee6ac1983937cc631ececf5bc277 Mon Sep 17 00:00:00 2001 >> From: Abhishek Tiwari >> Date: Tue, 28 Mar 2017 09:20:07 +0530 >> Subject: [PATCH v4] Fix missing

Re: [PATCH v4] Implemented -e trace=%clock option

ok. patched. On Tue, Mar 28, 2017 at 7:47 AM, Dmitry V. Levin wrote: > On Tue, Mar 28, 2017 at 03:42:04AM +0530, Rishi Bhatt wrote: > > From 294db67743eb8509383cf80887747016271dd32a Mon Sep 17 00:00:00 2001 > > From: Rishi Bhatt > > Date: Tue, 28 Mar 2017 03:31:24 +0530 > > Subject: [PATCH] Imp

Re: GSoC 2017 Introduction: Netlink socket parsers

I updated the patch[1] and the proposal draft[2]. Please provide some feedback. Thank you. [1]https://github.com/ppiao/strace/tree/nl-socket [2] https://docs.google.com/document/d/15cVdpdBP6jzEGP74tSG18ymi278_P2uv8MhRus-CuPI/edit?usp=sharing >On Tue, Mar 28, 2017 at 10:37 AM, Dmitry V. Levin wrot

Re: [PATCH v6] Implement -e trace=%statfs option for tracing statfs like syscalls

On Wed, Mar 29, 2017 at 4:50 AM, Dmitry V. Levin wrote: > On Tue, Mar 28, 2017 at 09:40:48AM +0530, Abhishek Tiwari wrote: >> >> Sir, >> >> the statfs64.test file calls the statfs.test itself. >> >> On adding 17 statfs64 to my test file gives error >> >> >> >> undefined: __NR_statfs64 >> > This is

strace 4.14 problem with "make check": msg_control and msg_control-v fail

Hi, I've built strace 4.14 successfully a hundred times, but a colleague on a remote system (I can't get to it) is seeing two of the "make check" tests fail, msg_control and msg_control-v. All the other tests run without error. The environment is

Re: strace 4.14 problem with "make check": msg_control and msg_control-v fail

Hi, On Wed, Mar 29, 2017 at 10:53:00AM -0400, Andy Riebs wrote: > Hi, > > I've built strace 4.14 successfully a hundred times, but a colleague > on a remote system (I can't get to it) is seeing two of the "make > check" tests fail, msg_control and msg_control-v. All the other

Re: strace 4.14 problem with "make check": msg_control and msg_control-v fail

Bingo! The problem system has that set to 4GiB, where msg_control.c looks for a max of 1GiB. Many thanks for your help! Andy On 03/29/2017 11:30 AM, Dmitry V. Levin wrote: > Hi, > > On Wed, Mar 29, 2017 at 10:53:00AM -0400, Andy Riebs wrote: >> Hi, >> >> I've built strace 4.14

Re: [PATCH] powerpc, x86_64: drop support of old kernels

On Tue, Mar 28, 2017 at 09:18:29PM +0300, Gleb Fotengauer-Malinovskiy wrote: > Drop support of x86_64 kernels < 2.6.34 > without PTRACE_GETREGSET support. I think dropping support for kernels like 2.6.32 this early is not a very good idea. At least, it's quite dramatic change from "Linux kernel >=

Re: [PATCH 1/3] xlat/v4l2*.in: updated v4l2 constants

On Wed, 29 Mar 2017 02:27:03 +0300 "Dmitry V. Levin" wrote: > On Tue, Mar 28, 2017 at 06:21:28PM +0300, Edgar Kaziahmedov wrote: > > As a new kernel version, commit adds additional > > defines to xlat/v4l2*.in files. > > It won't harm if you added the kernel version you are synchronising > xla

[PATCH 2/3] v4l2: printings for all buf types

* v4l2.c: add meaningful and informative printings for all v4l2 buf types in the 'print_v4l2_format_fmt' routine, implementation print_v4l2_clip routine to print the clips field in case of the overlay type buf * xlat/v4l2_vbi_flags.in: new flags for and V4L2_BUF_TYPE_VBI* * xlat/v4l2_sliced_flags.i

[PATCH 3/3] tests/ioctl_v4l2: extended tests

* tests/ioctl_v4l2.c: In accordance with changes made, this commit adds tests for the new functionality. Moreover, to avoid the "copy-paste" code for ioctl's requests like VIDIOC_TRY_FMT and VIDIOC_S_FMT there are special functions: init_v4l2_format, print_ioctl_v4l2. Signed-off-by: Edgar Kaziahme

[PATCH 1/3] xlat/v4l2*.in: update of various v4l2's flags

Linux 4.4: V4L2_BUF_TYPE_SDR_OUTPUT, V4L2_COLORSPACE_DCI_P3, V4L2_COLORSPACE_BT2020 Linux 4.2: V4L2_BUF_FLAG_LAST, V4L2_COLORSPACE_RAW Linux 3.8: V4L2_MEMORY_DMABUF Linux 3.6: V4L2_BUF_FLAG_INPUT is not useful Linux 3.19: V4L2_COLORSPACE_ADOBERGB Linux 3.17: V4L2_CAP_EXT_PIX_FORMAT Linux 3.15:

[PATCH v4 0/3]: v4l2 microproject (GSoC 2017)

Inhanced informativeness of the ioctl syscall(for the range of requests owned to v4l2) and tests. v1: just the first attempt to change(contained mistakes) v2: add all printings v3: fix some mistakes and add tests v4: fix several bugs, separate commits and rewrite tests

Re: A: sched_xetattr.test fails consistently on aarch64

On Tue, Mar 14, 2017 at 10:53:48AM +0300, Dmitry V. Levin wrote: > On Tue, Mar 14, 2017 at 01:16:23AM -0400, Mike Frysinger wrote: > > On 14 Mar 2017 00:57, Mike Frysinger wrote: > > > so there's a disagreement in the overall system somewhere. > > > i'd assume either the kernel's implementation of

Re: [PATCH] powerpc, x86_64: drop support of old kernels

On Wed, Mar 29, 2017 at 08:06:18PM +0200, Eugene Syromyatnikov wrote: > On Tue, Mar 28, 2017 at 09:18:29PM +0300, Gleb Fotengauer-Malinovskiy wrote: > > Drop support of x86_64 kernels < 2.6.34 > > without PTRACE_GETREGSET support. > I think dropping support for kernels like 2.6.32 this early is not

Re: [RFC] GSoC 2017 proposal draft: advanced syscall tampering and filtering with Lua

Hello. On Sat, Mar 25, 2017 at 10:58:16PM +0300, Victor Krapivensky wrote: > The first draft of my proposal can be found here: > > https://gist.github.com/shdown/a1f3f2bce1210f55389bacf406030b25 > > As for now, it is incomplete (does not even contain schedule) and will > surely be updated and en

Re: GSOC: Project Proposal

On Sat, Mar 25, 2017 at 12:56 PM, Abhishek Tiwari wrote: > On Fri, Mar 24, 2017 at 8:40 AM, Abhishek Tiwari > wrote: >> On Fri, Mar 24, 2017 at 7:59 AM, Dmitry V. Levin wrote: >>> Hi, >>> >>> On Sat, Mar 18, 2017 at 06:22:51PM +0530, Abhishek Tiwari wrote: Sir, I have gone through mail