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

On Wed, Mar 29, 2017 at 11:55:43PM +0300, Edgar Kaziahmedov wrote: > * 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 > *

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

On Wed, Mar 29, 2017 at 11:55:42PM +0300, Edgar Kaziahmedov wrote: > 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

Re: [PATCH 1/3] Add gdb remote protocol handling to strace

> I'm is in the process of reviewing/rewriting your patch. The main > issue here is that it is a bit intrusive and does so in a > backend-specific way. I already had an idea of introduction of > backend-neutral layer, in order to support uprobes. for example, and > your submission poked me again

Re: GSoC 2017: patch for the stat/nanosecond bug

On Mon, Apr 03, 2017 at 07:46:10PM +0300, Dmitry Savelyev wrote: > Hello. My name is Dmitry Savelyev and I'm a third year student at CMC MSU > looking to participate in this year's GSoC with strace. > > I have, of course, already submitted my proposal for netlink socket parsers, > although I did

[PATCH] stat: print nanoseconds immediately after seconds

* util.c: Implement a new sprinttime_nsec function for printing time_t and nanoseconds at once. * defs.h: Prototype for the above. * statx.c: Use it. * print_struct_stat.c: Likewise. * tests/print_time.c: Separate time_t printing functions with and without nanoseconds. * tests/tests.h: Prototype

GSoC 2017: patch for the stat/nanosecond bug

Hello. My name is Dmitry Savelyev and I'm a third year student at CMC MSU looking to participate in this year's GSoC with strace. I have, of course, already submitted my proposal for netlink socket parsers, although I did kind of screw it up in one part - namely I specified NETLINK_ARPD as one of

Re: GSOC 2017: Project Proposal

On Mon, Apr 03, 2017 at 09:26:59PM +0530, sandhya bankar wrote: > On Mon, Apr 3, 2017 at 9:10 PM, Eugene Syromiatnikov wrote: > > On Mon, Apr 03, 2017 at 08:51:34PM +0530, sandhya bankar wrote: > >> To deal with code coverage, I will run individual test cases to find > >> out why

Re: GSOC 2017: Project Proposal

On Mon, Apr 3, 2017 at 9:10 PM, Eugene Syromiatnikov wrote: > On Mon, Apr 03, 2017 at 08:51:34PM +0530, sandhya bankar wrote: >> To deal with code coverage, I will run individual test cases to find >> out why the coverage is below 100%. > > OK, let's be more specific: what are

Re: GSOC 2017: Project Proposal

On Mon, Apr 03, 2017 at 08:51:34PM +0530, sandhya bankar wrote: > To deal with code coverage, I will run individual test cases to find > out why the coverage is below 100%. OK, let's be more specific: what are your suggestions in regards of increasing coverage of dm.c up to 100%?

Re: GSOC 2017: Project Proposal

On Mon, Apr 3, 2017 at 8:32 PM, Eugene Syromiatnikov wrote: > On Mon, Apr 03, 2017 at 08:08:34PM +0530, sandhya bankar wrote: >> Please review my proposal link for the project "Comprehensive test suite" >> >>

Re: GSOC 2017: Project Proposal

On Mon, Apr 03, 2017 at 08:08:34PM +0530, sandhya bankar wrote: > Please review my proposal link for the project "Comprehensive test suite" > > https://docs.google.com/document/d/1RY5cdJGb0UVN-5q5imuwrcVnFRlVgM0Rx3okdrfkxTU/edit?usp=sharing Can you please provide information regarding the

GSOC 2017: Project Proposal

Hello, Please review my proposal link for the project "Comprehensive test suite" https://docs.google.com/document/d/1RY5cdJGb0UVN-5q5imuwrcVnFRlVgM0Rx3okdrfkxTU/edit?usp=sharing Thanks, Sandhya -- Check out the

Re: GSoC 2017: proposal v2

On Mon, 3 Apr 2017 17:20:32 +0300 "Dmitry V. Levin" wrote: > On Mon, Apr 03, 2017 at 05:06:02PM +0300, Edgar Kaziahmedov wrote: > > On Mon, 3 Apr 2017 15:46:03 +0300, Dmitry V. Levin wrote: > > > On Mon, Apr 03, 2017 at 02:35:17PM +0200, Eugene Syromiatnikov > > > wrote: >

Re: GSoC 2017: proposal v2

On Mon, Apr 03, 2017 at 05:06:02PM +0300, Edgar Kaziahmedov wrote: > On Mon, 3 Apr 2017 15:46:03 +0300, Dmitry V. Levin wrote: > > On Mon, Apr 03, 2017 at 02:35:17PM +0200, Eugene Syromiatnikov wrote: > > > On Sun, Apr 02, 2017 at 04:29:36AM +0300, Edgar Kaziahmedov wrote: > > > >

Re: GSoC 2017: proposal v2

On Mon, 3 Apr 2017 15:46:03 +0300 "Dmitry V. Levin" wrote: > On Mon, Apr 03, 2017 at 02:35:17PM +0200, Eugene Syromiatnikov wrote: > > On Sun, Apr 02, 2017 at 04:29:36AM +0300, Edgar Kaziahmedov wrote: > > > https://github.com/edosedgar/xs-pkg/blob/master/proposal.txt > > > >

Re: GSoC 2017: proposal v2

On Mon, Apr 03, 2017 at 02:35:17PM +0200, Eugene Syromiatnikov wrote: > On Sun, Apr 02, 2017 at 04:29:36AM +0300, Edgar Kaziahmedov wrote: > > https://github.com/edosedgar/xs-pkg/blob/master/proposal.txt > > The other thing (besides syscallents.h) I think might useful to leverage > is the current

Re: GSoC 2017: proposal v2

On Sun, Apr 02, 2017 at 04:29:36AM +0300, Edgar Kaziahmedov wrote: > https://github.com/edosedgar/xs-pkg/blob/master/proposal.txt The other thing (besides syscallents.h) I think might useful to leverage is the current syscall filtering mechanism, so it would be possible to check out which system

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

On Thu, Mar 30, 2017 at 5:56 PM, Victor Krapivensky wrote: > On Thu, Mar 30, 2017 at 05:28:55AM +0200, Eugene Syromyatnikov wrote: >> The one quite interesting aspect, from my point of view, is the way you >> expect to access (and modify) argument data. For example,

GSoC 2017: deadline for students to submit their Final PDF proposal

Hi, This is a kind reminder to students that the deadline to submit their Final PDF proposal is Monday, April 3rd at 16:00 UTC. Note that there is no deadline set for microprojects, so they can continue after the deadline for proposals. -- ldv signature.asc Description: PGP signature

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

On Mon, Apr 03, 2017 at 12:12:24PM +0300, Edgar Kaziahmedov wrote: > On Wed, 29 Mar 2017 23:55:41 +0300, Edgar Kaziahmedov wrote: > > > Inhanced informativeness of the ioctl syscall(for the range of > > requests owned to v4l2) and tests. > > > > v1: just the first attempt to change(contained

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

On Wed, 29 Mar 2017 23:55:41 +0300 Edgar Kaziahmedov wrote: > 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