Re: GSoC: Introduction

2017-03-25 Thread Israel vianney
On Mar 20, 2017 19:54, "Israel vianney" wrote: On Sat, Mar 18, 2017 at 2:22 AM, Dmitry V. Levin wrote: > On Fri, Mar 17, 2017 at 08:36:45PM +0100, Israel vianney wrote: > [...] > > Please I 've gone through the tests and test folder in the source code > > trying to understand the used format,

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-21 Thread Eugene Syromyatnikov
On Sat, Mar 18, 2017 at 08:29:46PM +0530, Abhishek Tiwari wrote: > fixed. Patch attached. Please look at the rest of the e-mail you have replied to. -- Check out the vibrant tech community on one of the world's most engagi

Re: GSoC: Introduction

2017-03-20 Thread Israel vianney
On Sat, Mar 18, 2017 at 2:22 AM, Dmitry V. Levin wrote: > On Fri, Mar 17, 2017 at 08:36:45PM +0100, Israel vianney wrote: > [...] > > Please I 've gone through the tests and test folder in the source code > > trying to understand the used format, I also checked on codecov what is > > left to be d

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-18 Thread Abhishek Tiwari
>> Below is attached a patch corresonding to -e trace=%statfs option. >> Please review. > > git am patch fails to apply this patch with the following diagnostics: > > .git/rebase-apply/patch:778: trailing whitespace. > 17 statfs > fatal: 1 line adds whitespace errors. > fixed. Patch attached. > >

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-18 Thread Eugene Syromyatnikov
On Sat, Mar 18, 2017 at 05:57:39PM +0530, Abhishek Tiwari wrote: > On Sat, Mar 18, 2017 at 3:53 PM, Eugene Syromyatnikov > wrote: > > > So, after some thinking, I have the following scheme in mind: > > > > {old,}stat{,64} TRACE_STAT TST > %stat > > > {old,}lstat{,64}

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-18 Thread Abhishek Tiwari
On Sat, Mar 18, 2017 at 3:53 PM, Eugene Syromyatnikov wrote: > So, after some thinking, I have the following scheme in mind: > > {old,}stat{,64} TRACE_STAT TST %stat > {old,}lstat{,64}TRACE_LSTAT TLST %lstat > {old,new,}fstat{,at}64 TRACE_FSTAT

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-18 Thread Eugene Syromyatnikov
On Sat, Mar 18, 2017 at 02:49:48PM +0530, Abhishek Tiwari wrote: > Going with the above description for narrow statfs-> > > Is naming %statfs = statfs+statfs64 as TRACE_NSTATFS and shorthand as TNS > fine ? So, after some thinking, I have the following scheme in mind: {old,}stat{,64} TR

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-18 Thread Abhishek Tiwari
On Sat, Mar 18, 2017 at 2:09 PM, Eugene Syromyatnikov wrote: > On Thu, Mar 16, 2017 at 12:24 AM, Dmitry V. Levin wrote: >> On Wed, Mar 15, 2017 at 11:14:29PM +0530, Abhishek Tiwari wrote: >> [...] >>> Is it fine to group statfs+ statfs64+ fstatfs + fstatfs64 + ustat as >>> %statfs or it should b

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-18 Thread Eugene Syromyatnikov
On Thu, Mar 16, 2017 at 12:24 AM, Dmitry V. Levin wrote: > On Wed, Mar 15, 2017 at 11:14:29PM +0530, Abhishek Tiwari wrote: > [...] >> Is it fine to group statfs+ statfs64+ fstatfs + fstatfs64 + ustat as >> %statfs or it should be (statfs+statfs64 + ustat) and >> (fstatfs+ftsatfs64) i.e. two diff

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-17 Thread Abhishek Tiwari
On Thu, Mar 16, 2017 at 11:33 PM, Abhishek Tiwari wrote: > On Thu, Mar 16, 2017 at 5:54 AM, Dmitry V. Levin wrote: >> On Wed, Mar 15, 2017 at 11:14:29PM +0530, Abhishek Tiwari wrote: >> [...] >>> Is it fine to group statfs+ statfs64+ fstatfs + fstatfs64 + ustat as >>> %statfs or it should be (st

Re: GSoC: Introduction

2017-03-17 Thread Dmitry V. Levin
On Fri, Mar 17, 2017 at 08:36:45PM +0100, Israel vianney wrote: [...] > Please I 've gone through the tests and test folder in the source code > trying to understand the used format, I also checked on codecov what is > left to be done as for the testing, then noticed some files with 100% miss > but

Re: GSOC: Introduction

2017-03-17 Thread Eugene Syromyatnikov
On Thu, Mar 16, 2017 at 10:07:27PM +0530, Abhishek Tiwari wrote: > From 38ea98c7ba87bc485d8af34fc401f46b05b2c035 Mon Sep 17 00:00:00 2001 > From: Abhishek Tiwari > Date: Thu, 16 Mar 2017 16:55:44 +0530 > Subject: [PATCH v4] Implement -e trace=%statfs option for tracing statfs like > syscalls. >

Re: GSoC: Introduction

2017-03-17 Thread Israel vianney
Hi On Mar 13, 2017 18:44, "Dmitry V. Levin" wrote: Hi, On Sun, Mar 12, 2017 at 06:55:44AM +0100, Israel vianney wrote: > Hi, > > I am Vianney Israel a second year undergraduate computer science student in > ISICOM University from Cameroon. I am new to open-source and i wish to > contribute to S

Re: Gsoc Introduction.

2017-03-17 Thread Eugene Syromyatnikov
On Fri, Mar 17, 2017 at 06:35:09PM +0100, Eugene Syromyatnikov wrote: > Please format function declaration as following: > > int > nsfs_ioctl(struct tcb *tcp, unsigned int code, kernel_ulong_t arg) { Oops. Opening curly brace should be on the next line, like this: int nsfs_ioctl(struct tcb *tcp,

Re: Gsoc Introduction.

2017-03-17 Thread Eugene Syromyatnikov
On Fri, Mar 17, 2017 at 08:12:02AM +0700, Nikolay Marchuk wrote: > Thank you for review. I have rewritten my code, but I still have some > problems with NS_GET_NSTYPE parsing without additional argument. And new > tests are not fully tested, because I haven't build kernel yet. Please send patches

Re: Gsoc Introduction.

2017-03-16 Thread Nikolay Marchuk
Thank you for review. I have rewritten my code, but I still have some problems with NS_GET_NSTYPE parsing without additional argument. And new tests are not fully tested, because I haven't build kernel yet. On Thu, Mar 16, 2017 at 9:01 AM, Dmitry V. Levin wrote: > On Wed, Mar 15, 2017 at 03:22:3

Re: Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-16 Thread Abhishek Tiwari
On Thu, Mar 16, 2017 at 5:54 AM, Dmitry V. Levin wrote: > On Wed, Mar 15, 2017 at 11:14:29PM +0530, Abhishek Tiwari wrote: > [...] >> Is it fine to group statfs+ statfs64+ fstatfs + fstatfs64 + ustat as >> %statfs or it should be (statfs+statfs64 + ustat) and >> (fstatfs+ftsatfs64) i.e. two diffe

Re: GSOC: Introduction

2017-03-16 Thread Abhishek Tiwari
On Thu, Mar 16, 2017 at 9:53 AM, Abhishek Tiwari wrote: > On Wed, Mar 15, 2017 at 11:14 PM, Abhishek Tiwari > wrote: >> On Tue, Mar 14, 2017 at 8:44 AM, Abhishek Tiwari >> wrote: >>> On Tue, Mar 14, 2017 at 2:00 AM, Dmitry V. Levin wrote: On Tue, Mar 14, 2017 at 12:40:46AM +0530, Abhishek

Re: GSOC: Introduction

2017-03-15 Thread Abhishek Tiwari
On Wed, Mar 15, 2017 at 11:14 PM, Abhishek Tiwari wrote: > On Tue, Mar 14, 2017 at 8:44 AM, Abhishek Tiwari > wrote: >> On Tue, Mar 14, 2017 at 2:00 AM, Dmitry V. Levin wrote: >>> On Tue, Mar 14, 2017 at 12:40:46AM +0530, Abhishek Tiwari wrote: > Per-file summary is not in GNU change log fo

Re: Gsoc Introduction.

2017-03-15 Thread Dmitry V. Levin
On Wed, Mar 15, 2017 at 03:22:36PM +0700, Nikolay Marchuk wrote: > Hello, > I have implemented NS_* ioctls. Should I use common ioctlent interface to > print them with additional argument or should I print them without it? Why do you think printing additional arguments makes any sense? > From f03

Q: statfs related syscalls (was: Re: GSOC: Introduction)

2017-03-15 Thread Dmitry V. Levin
On Wed, Mar 15, 2017 at 11:14:29PM +0530, Abhishek Tiwari wrote: [...] > Is it fine to group statfs+ statfs64+ fstatfs + fstatfs64 + ustat as > %statfs or it should be (statfs+statfs64 + ustat) and > (fstatfs+ftsatfs64) i.e. two different classes ? Well, I don't have a ready answer to this questi

Re: GSOC: Introduction

2017-03-15 Thread Abhishek Tiwari
On Tue, Mar 14, 2017 at 8:44 AM, Abhishek Tiwari wrote: > On Tue, Mar 14, 2017 at 2:00 AM, Dmitry V. Levin wrote: >> On Tue, Mar 14, 2017 at 12:40:46AM +0530, Abhishek Tiwari wrote: >>> > Per-file summary is not in GNU change log format, please refer to >>> > https://www.gnu.org/prep/standards/ht

Re: Gsoc Introduction.

2017-03-15 Thread Nikolay Marchuk
Hello, I have implemented NS_* ioctls. Should I use common ioctlent interface to print them with additional argument or should I print them without it? On Tue, Mar 14, 2017 at 9:21 AM, Dmitry V. Levin wrote: > Hi, > > On Tue, Mar 14, 2017 at 08:35:45AM +0700, Николай Марчук wrote: > > Hello, > >

Re: GSOC: Introduction

2017-03-13 Thread Abhishek Tiwari
On Tue, Mar 14, 2017 at 2:00 AM, Dmitry V. Levin wrote: > On Tue, Mar 14, 2017 at 12:40:46AM +0530, Abhishek Tiwari wrote: >> > Per-file summary is not in GNU change log format, please refer to >> > https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html . >> > Specifically, it lack

Re: Gsoc Introduction.

2017-03-13 Thread Dmitry V. Levin
Hi, On Tue, Mar 14, 2017 at 08:35:45AM +0700, Николай Марчук wrote: > Hello, > my name is Nikolay Marchuk and I am a first-year student in NSU, Russia. I > want to implement advanced filtering syntax for strace. I am familiar with > c and c++ and have an experience of making parsers. Thanks for s

Gsoc Introduction.

2017-03-13 Thread Николай Марчук
Hello, my name is Nikolay Marchuk and I am a first-year student in NSU, Russia. I want to implement advanced filtering syntax for strace. I am familiar with c and c++ and have an experience of making parsers. I wanted to add support of new ioctl commands from linux 4.9 - 4.11 as my introduction mic

Re: GSOC: Introduction

2017-03-13 Thread Dmitry V. Levin
On Tue, Mar 14, 2017 at 12:40:46AM +0530, Abhishek Tiwari wrote: > > Per-file summary is not in GNU change log format, please refer to > > https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html . > > Specifically, it lacks asterisks at the beginning of each new file > > description

Re: GSoC: Introduction

2017-03-13 Thread Dmitry V. Levin
Hi, On Sun, Mar 12, 2017 at 06:55:44AM +0100, Israel vianney wrote: > Hi, > > I am Vianney Israel a second year undergraduate computer science student in > ISICOM University from Cameroon. I am new to open-source and i wish to > contribute to Strace as for Gsoc 2017. > I am familiar with C, git a

Re: GSOC: Introduction

2017-03-12 Thread Eugene Syromyatnikov
> Thank you for the patch acceptance. > Is the following list of open system calls complete ? It is based on > reply that function calls that returns new file descriptor > > 1) mq_open > 2) openat > 3) perf_event_open > 4) open_by_handle_at > 5) memfd_create > 6) epoll_create1 > 7) dup > 8) dup3 >

Re: GSOC: Introduction

2017-03-12 Thread Eugene Syromyatnikov
On Sat, Mar 11, 2017 at 02:26:42PM +0530, Abhishek Tiwari wrote: > On Sat, Mar 11, 2017 at 1:46 PM, Abhishek Tiwari > wrote: > > Sir, I figured out that open system call is implemented corresponding > > to kernel version it supports, so open syscall is inside > > linux/x32/syscallent.h while opena

GSoC: Introduction

2017-03-11 Thread Israel vianney
Hi, I am Vianney Israel a second year undergraduate computer science student in ISICOM University from Cameroon. I am new to open-source and i wish to contribute to Strace as for Gsoc 2017. I am familiar with C, git and system/shell programming. Also, i have cloned and build the strace code base

Re: GSOC: Introduction

2017-03-11 Thread Abhishek Tiwari
On Sat, Mar 11, 2017 at 1:46 PM, Abhishek Tiwari wrote: > Sir, I figured out that open system call is implemented corresponding > to kernel version it supports, so open syscall is inside > linux/x32/syscallent.h while openat is used in later versions. > Please verify that the open-like system call

Re: GSOC: Introduction

2017-03-11 Thread Abhishek Tiwari
Sir, I figured out that open system call is implemented corresponding to kernel version it supports, so open syscall is inside linux/x32/syscallent.h while openat is used in later versions. Please verify that the open-like system call list is complete. Implemented -e trace=%stat class and submitti

Re: GSOC: Introduction

2017-03-10 Thread Abhishek Tiwari
> Thank you for the patch acceptance. > Is the following list of open system calls complete ? It is based on > reply that function calls that returns new file descriptor > > 1) mq_open > 2) openat > 3) perf_event_open > 4) open_by_handle_at > 5) memfd_create > 6) epoll_create1 > 7) dup > 8) dup3 >

Re: GSOC: Introduction

2017-03-10 Thread Abhishek Tiwari
On Thu, Mar 9, 2017 at 5:39 AM, Dmitry V. Levin wrote: > On Wed, Mar 08, 2017 at 07:51:49AM +0530, Abhishek Tiwari wrote: >> Made changes in description of commit message and INSTALL-git.md. >> From bfb8f2576e947b8b1abd7709f1ae8277d77e3c2a Mon Sep 17 00:00:00 2001 >> From: Abhishek Tiwari >> Date

Re: GSOC: Introduction

2017-03-08 Thread Dmitry V. Levin
On Wed, Mar 08, 2017 at 07:51:49AM +0530, Abhishek Tiwari wrote: > Made changes in description of commit message and INSTALL-git.md. > From bfb8f2576e947b8b1abd7709f1ae8277d77e3c2a Mon Sep 17 00:00:00 2001 > From: Abhishek Tiwari > Date: Tue, 7 Mar 2017 08:49:30 +0530 > Subject: [PATCH v6] Updated

Re: GSOC: Introduction

2017-03-07 Thread Eugene Syromyatnikov
> What unix system calls are to be grouped as open-like system calls? I'd assume that open-like system call is a system call which returns new fd, but others' interpretations may vary. > and I can't find open system call inside linux/32/syscallent.h ? open(path, flags, mode) can be implemented as

Re: GSOC: Introduction

2017-03-07 Thread Abhishek Tiwari
On Tue, Mar 7, 2017 at 3:01 AM, Dmitry V. Levin wrote: > On Mon, Mar 06, 2017 at 08:35:07PM +0530, Abhishek Tiwari wrote: > [...] >> Updated patch file is attached. Please review. >> From 79cfa5613d90c87e0b29ada3a7075eb0660d19b8 Mon Sep 17 00:00:00 2001 >> From: Abhishek Tiwari >> Date: Mon, 6 M

Re: GSOC: Introduction

2017-03-06 Thread Dmitry V. Levin
On Mon, Mar 06, 2017 at 08:35:07PM +0530, Abhishek Tiwari wrote: [...] > Updated patch file is attached. Please review. > From 79cfa5613d90c87e0b29ada3a7075eb0660d19b8 Mon Sep 17 00:00:00 2001 > From: Abhishek Tiwari > Date: Mon, 6 Mar 2017 20:21:23 +0530 > Subject: [PATCH v5] Updated information

Re: GSOC: Introduction

2017-03-06 Thread Abhishek Tiwari
On Mon, Mar 6, 2017 at 3:43 PM, Dmitry V. Levin wrote: > On Mon, Mar 06, 2017 at 02:40:48PM +0530, Abhishek Tiwari wrote: > [...] >> Corrected format of the commit message and performed rebase. Please >> review the attached patch > >> From 0ab59994b2e24e85734cbe14200f31f3e4d4e4e1 Mon Sep 17 00:00:

Re: GSOC: Introduction

2017-03-06 Thread Dmitry V. Levin
On Mon, Mar 06, 2017 at 02:40:48PM +0530, Abhishek Tiwari wrote: [...] > Corrected format of the commit message and performed rebase. Please > review the attached patch > From 0ab59994b2e24e85734cbe14200f31f3e4d4e4e1 Mon Sep 17 00:00:00 2001 > From: Abhishek Tiwari > Date: Mon, 6 Mar 2017 11:48:5

Re: GSOC: Introduction

2017-03-06 Thread Abhishek Tiwari
On Mon, Mar 6, 2017 at 3:20 AM, Dmitry V. Levin wrote: > On Mon, Mar 06, 2017 at 03:00:05AM +0530, Abhishek Tiwari wrote: >> On Mon, Mar 6, 2017 at 12:43 AM, Dmitry V. Levin wrote: >> > On Sun, Mar 05, 2017 at 06:27:49PM +0530, Abhishek Tiwari wrote: >> >> On Sun, Mar 5, 2017 at 8:48 AM, Dmitry V.

Re: GSOC: Introduction

2017-03-05 Thread Dmitry V. Levin
On Mon, Mar 06, 2017 at 03:00:05AM +0530, Abhishek Tiwari wrote: > On Mon, Mar 6, 2017 at 12:43 AM, Dmitry V. Levin wrote: > > On Sun, Mar 05, 2017 at 06:27:49PM +0530, Abhishek Tiwari wrote: > >> On Sun, Mar 5, 2017 at 8:48 AM, Dmitry V. Levin wrote: > >> > On Sun, Mar 05, 2017 at 01:54:33AM +0530

Re: GSOC: Introduction

2017-03-05 Thread Abhishek Tiwari
On Mon, Mar 6, 2017 at 12:43 AM, Dmitry V. Levin wrote: > On Sun, Mar 05, 2017 at 06:27:49PM +0530, Abhishek Tiwari wrote: >> On Sun, Mar 5, 2017 at 8:48 AM, Dmitry V. Levin wrote: >> > On Sun, Mar 05, 2017 at 01:54:33AM +0530, Abhishek Tiwari wrote: >> >> On Sat, Mar 4, 2017 at 5:41 PM, Abhishek

Re: GSOC: Introduction

2017-03-05 Thread Dmitry V. Levin
On Sun, Mar 05, 2017 at 06:27:49PM +0530, Abhishek Tiwari wrote: > On Sun, Mar 5, 2017 at 8:48 AM, Dmitry V. Levin wrote: > > On Sun, Mar 05, 2017 at 01:54:33AM +0530, Abhishek Tiwari wrote: > >> On Sat, Mar 4, 2017 at 5:41 PM, Abhishek Tiwari wrote: > >> > Good evening everyone, > >> > I am Abhish

Re: GSOC: Introduction

2017-03-05 Thread Abhishek Tiwari
. On Sun, Mar 5, 2017 at 8:48 AM, Dmitry V. Levin wrote: > Hi, > > On Sun, Mar 05, 2017 at 01:54:33AM +0530, Abhishek Tiwari wrote: >> On Sat, Mar 4, 2017 at 5:41 PM, Abhishek Tiwari >> wrote: >> > Good evening everyone, >> > I am Abhishek Tiwari pursuing M.Tech IIT Kharagpur. I am looking >> >

Re: GSOC: Introduction

2017-03-04 Thread Dmitry V. Levin
Hi, On Sun, Mar 05, 2017 at 01:54:33AM +0530, Abhishek Tiwari wrote: > On Sat, Mar 4, 2017 at 5:41 PM, Abhishek Tiwari > wrote: > > Good evening everyone, > > I am Abhishek Tiwari pursuing M.Tech IIT Kharagpur. I am looking > > forward to contribute to strace Project Idea -> Netlink socket > > pa

Re: GSOC: Introduction

2017-03-04 Thread Abhishek Tiwari
On Sat, Mar 4, 2017 at 5:41 PM, Abhishek Tiwari wrote: > Good evening everyone, > I am Abhishek Tiwari pursuing M.Tech IIT Kharagpur. I am looking > forward to contribute to strace Project Idea -> Netlink socket > parsers. > > Thank you. Hi, I have made a change in INSTALL file (there the boots

GSOC: Introduction

2017-03-04 Thread Abhishek Tiwari
Good evening everyone, I am Abhishek Tiwari pursuing M.Tech IIT Kharagpur. I am looking forward to contribute to strace Project Idea -> Netlink socket parsers. Thank you. -- Check out the vibrant tech community on one of

[GSOC] Introduction

2016-05-03 Thread Fabien Siron
Hi list, First, I would like to thank you for having selected me for the GSOC. My name is Fabien Siron. I am a french CS student living in Paris and I really wanted to use the LSE (Security/System Epita laboratory) fellowship opportunity to participate at the GSOC. My subject is *Netlink socket p

GSOC: Introduction + Cannot locate strace_GSOC2014

2015-03-19 Thread haris iqbal
Hello guys, I went through the ideas list in the strace website and i am interested in the *"Structured output*" of strace. I am currently pursuing Masters in Information Technology in National Institute of Technology Karnataka (NITK), India. I am about to finish my first year. I have a good exper