Re: Introduction

2018-01-05 Thread Kommuru jai shankar reddy
On git grep -l RVAL_IOCTL_DECODED, i got block.c btrfs.c defs.h dm.c evdev.c file_ioctl.c fs_x_ioctl.c hdio.c ioctl.c kvm.c loop.c mtd.c nsfs.c print_sg_req_info.c ptp.c rtc.c scsi.c sg_io_v3.c sg_io_v4.c sock.c term.c ubi.c userfaultfd.c v4l2.c With which one, should i start adding tests

Re: Introduction

2018-01-03 Thread Dmitry V. Levin
On Thu, Dec 28, 2017 at 07:49:23PM +0530, Kommuru jai shankar reddy wrote: > I have a doubt: > There are three files file_ioctl.c, fs_x_ioctl.c and ioctl.c in > the https://codecov.io/github/strace/strace with their code coverages. Firstly, most of ioctl decoders are not in these three fi

Re: Introduction

2018-01-03 Thread Kommuru jai shankar reddy
Can I be provided help in my above doubt and the internal workings of strace On Thu, Dec 28, 2017 at 7:49 PM, Kommuru jai shankar reddy < kommurujaishankarre...@gmail.com> wrote: > I have a doubt: > There are three files file_ioctl.c, fs_x_ioctl.c and ioctl.c in > the https://codecov.io/

Re: Introduction

2017-12-28 Thread Kommuru jai shankar reddy
I have a doubt: There are three files file_ioctl.c, fs_x_ioctl.c and ioctl.c in the https://codecov.io/github/strace/strace with their code coverages. Now I have to find the corresponding test files in the strace/tests/ and modify them to increase the code coverage right ? please correct

Re: Introduction

2017-12-27 Thread Chen Jingpiao
On 12/26 10:53, Harsha Sharma wrote: > On Tue, Dec 26, 2017 at 9:49 AM, Chen Jingpiao wrote: > > On 12/25 10:26, Harsha Sharma wrote: > >> On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen wrote: > >> > On 12/25 06:12, Harsha Sharma wrote: > >> >> Hello everyone, > >> > > >> > Hi. > >> > > >> >> I'm

Re: Introduction

2017-12-26 Thread Harsha Sharma
On Tue, Dec 26, 2017 at 9:49 AM, Chen Jingpiao wrote: > On 12/25 10:26, Harsha Sharma wrote: >> On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen >> wrote: >> > On 12/25 06:12, Harsha Sharma wrote: >> >> Hello everyone, >> > >> > Hi. >> > >> >> I'm Harsha Sharma, a sophomore student at Indian Insti

Re: Introduction

2017-12-26 Thread Eugene Syromyatnikov
On Tue, Dec 26, 2017 at 1:44 PM, Kommuru jai shankar reddy wrote: > Yes, I am interested in the micro project of adding tests to the test > suite. Could you please provide suggestions on getting started to this ? Sure. I'd suggest starting with ioctl decoders that are not shown as covered in L

Re: Introduction

2017-12-26 Thread Kommuru jai shankar reddy
Yes, I am interested in the micro project of adding tests to the test suite. Could you please provide suggestions on getting started to this ? On Mon, Dec 25, 2017 at 11:49 PM, Eugene Syromyatnikov wrote: > On Mon, Dec 25, 2017 at 5:06 PM, Kommuru jai shankar reddy > wrote: > > Hello, > >

Re: Introduction

2017-12-25 Thread Chen Jingpiao
On 12/25 10:26, Harsha Sharma wrote: > On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen wrote: > > On 12/25 06:12, Harsha Sharma wrote: > >> Hello everyone, > > > > Hi. > > > >> I'm Harsha Sharma, a sophomore student at Indian Institute of > >> Technology, Roorkee, India. > >> I have knowledge of C

Re: Introduction

2017-12-25 Thread Eugene Syromyatnikov
On Mon, Dec 25, 2017 at 5:06 PM, Kommuru jai shankar reddy wrote: > Hello, >I'm jaya shankar,. Computer science student of national institute of > technology andhra pradesh, India > I have used strace for my mini project for tracing system calls of malware > executables and it helped me a

Introduction

2017-12-25 Thread Kommuru jai shankar reddy
Hello, I'm jaya shankar,. Computer science student of national institute of technology andhra pradesh, India I have used strace for my mini project for tracing system calls of malware executables and it helped me a lot. I want to contribute to the community and apply as student for GSOC 2k18

Re: Introduction

2017-12-25 Thread Harsha Sharma
On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen wrote: > On 12/25 06:12, Harsha Sharma wrote: >> Hello everyone, > > Hi. > >> I'm Harsha Sharma, a sophomore student at Indian Institute of >> Technology, Roorkee, India. >> I have knowledge of C, git, shell programming, kernel programming, gdb >> an

Re: Introduction

2017-12-25 Thread JingPiao Chen
On 12/25 06:12, Harsha Sharma wrote: > Hello everyone, Hi. > I'm Harsha Sharma, a sophomore student at Indian Institute of > Technology, Roorkee, India. > I have knowledge of C, git, shell programming, kernel programming, gdb > and parsers and currently working as outreachy intern in Linux-kerne

Introduction

2017-12-25 Thread Harsha Sharma
Hello everyone, I'm Harsha Sharma, a sophomore student at Indian Institute of Technology, Roorkee, India. I have knowledge of C, git, shell programming, kernel programming, gdb and parsers and currently working as outreachy intern in Linux-kernel (project nftables - Network filtration tool). Strac

Re: Introduction

2017-11-19 Thread Eugene Syromyatnikov
On Sun, Nov 19, 2017 at 4:32 PM, gou4shi1 wrote: > Thanks for you response. > > However, there are so many files, how can I get the overall structure of the > project? Most of the files contain decoders for specific syscalls (like mount.c, statx.c, getcpu.c, and so on) or groups of syscalls (like

Re: Introduction

2017-11-19 Thread gou4shi1
Thanks for you response. However, there are so many files, how can I get the overall structure of the project? or another simpler question, which file is the entry of strace?(because maybe I can start from this file) I am new to open source project, thanks for your help again. On Sun, Nov

Re: Introduction

2017-11-19 Thread Eugene Syromyatnikov
On Sun, Nov 19, 2017 at 1:49 PM, gou4shi1 wrote: > Hello everyone Hello. > I'm Guangqing Chen, an undergraduate from South China Normal University, > China. > > I have some knowledge about C and Unix programming. > > I want to know how to get started to read the source code of strace. Thank you

Introduction

2017-11-19 Thread gou4shi1
Hello everyone I'm Guangqing Chen, an undergraduate from South China Normal University, China. I have some knowledge about C and Unix programming. I want to know how to get started to read the source code of strace. Thanks for your reading. ---

Re: Introduction

2017-11-18 Thread Eugene Syromyatnikov
On Sat, Nov 18, 2017 at 8:38 PM, Manvendra Singh wrote: > Hi everyone Hello. > I'm Manvendra Singh and doing under-graduation in Computer Science & > Engineering from ITM University, Gwalior, India. > > I have knowledge of C, git and shell programming(basic). I wanted to > contribute to the commu

Introduction

2017-11-18 Thread Manvendra Singh
Hi everyone I'm Manvendra Singh and doing under-graduation in Computer Science & Engineering from ITM University, Gwalior, India. I have knowledge of C, git and shell programming(basic). I wanted to contribute to the community. Can anybody please help me get started. Being a college undergrad I'

Re: GSoC 2017 Introduction: Netlink socket parsers

2017-04-18 Thread JingPiao Chen
On Mon, Apr 17, 2017 at 9:40 PM, Dmitry V. Levin wrote: >On Wed, Mar 29, 2017 at 05:39:59PM +0800, JingPiao Chen wrote: >> I updated the patch[1] and the proposal draft[2]. >> Please provide some feedback. >> [1]https://github.com/ppiao/strace/tree/nl-socket > >As I said, every logically separate c

Re: GSoC 2017 Introduction: Netlink socket parsers

2017-04-17 Thread Dmitry V. Levin
On Wed, Mar 29, 2017 at 05:39:59PM +0800, JingPiao Chen wrote: > I updated the patch[1] and the proposal draft[2]. > Please provide some feedback. > [1]https://github.com/ppiao/strace/tree/nl-socket As I said, every logically separate change must go to an individual commit, the way Fabien did in h

Re: GSoC 2017 Introduction: Netlink socket parsers

2017-03-29 Thread JingPiao Chen
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: GSoC 2017 Introduction: Netlink socket parsers

2017-03-27 Thread JingPiao Chen
On Tue, Mar 28, 2017 at 10:37 AM, Dmitry V. Levin wrote: >On Mon, Mar 27, 2017 at 10:40:05PM +0800, JingPiao Chen wrote: >> 2017-03-27 6:16 GMT+08:00 Dmitry V. Levin wrote: >> >On Sun, Mar 19, 2017 at 12:25:11PM +0800, JingPiao Chen wrote: >> >> Hello strace-developers: >> >> My name is JingPiao C

Re: GSoC 2017 Introduction: Netlink socket parsers

2017-03-27 Thread Dmitry V. Levin
On Mon, Mar 27, 2017 at 10:40:05PM +0800, JingPiao Chen wrote: > 2017-03-27 6:16 GMT+08:00 Dmitry V. Levin wrote: > >On Sun, Mar 19, 2017 at 12:25:11PM +0800, JingPiao Chen wrote: > >> Hello strace-developers: > >> My name is JingPiao Chen. I'am a Computer Science sophomore from > >> Guangdong Pha

Re: GSoC 2017 Introduction: Netlink socket parsers

2017-03-27 Thread JingPiao Chen
>Hi, 2017-03-27 6:16 GMT+08:00 Dmitry V. Levin wrote: >On Sun, Mar 19, 2017 at 12:25:11PM +0800, JingPiao Chen wrote: >> Hello strace-developers: >> My name is JingPiao Chen. I'am a Computer Science sophomore from >> Guangdong Pharmaceutical University. I am interested in Netlink socket >> parsers

Re: GSoC 2017 Introduction: Netlink socket parsers

2017-03-26 Thread Dmitry V. Levin
Hi, On Sun, Mar 19, 2017 at 12:25:11PM +0800, JingPiao Chen wrote: > Hello strace-developers: > My name is JingPiao Chen. I'am a Computer Science sophomore from > Guangdong Pharmaceutical University. I am interested in Netlink socket > parsers suggested by Gabriel Laskar and Dmitry V. Levin. I am

Re: GSoC 2017 Introduction: Netlink socket parsers

2017-03-25 Thread JingPiao Chen
>Hello strace-developers: > My name is JingPiao Chen. I'am a Computer Science sophomore from >Guangdong Pharmaceutical University. I am interested in Netlink socket >parsers suggested by Gabriel Laskar and Dmitry V. Levin. I am familiar >with C, git, shell script, and gdb. > >My current work base o

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: Introduction and [PATCH V1]

2017-03-24 Thread Eugene Syromyatnikov
On Fri, Mar 24, 2017 at 8:12 AM, Rohan Rajak wrote: > Hi Sir, > > I am not really understanding whether we are covering majority of strace > code and kernel as well. Well, covering the kernel code is not a target of the test suite. Test suite is aimed to check that strace's behaviour is correct (i

Re: Introduction and [PATCH V1]

2017-03-24 Thread Rohan Rajak
Hi Sir, I am not really understanding whether we are covering majority of strace code and kernel as well. Also there is a difference of coverage on codecov site and on other systems I have tested, how would you suggest to solve that . On Wed, Mar 22, 2017 at 7:30 AM, Eugene Syromyatnikov wrote:

Re: Introduction and [PATCH V1]

2017-03-21 Thread Eugene Syromyatnikov
On Sun, Mar 19, 2017 at 03:27:18PM +0530, Rohan Rajak wrote: > Hi, > I am Rohan Rajak a 3rd year computer science student at IIT Kharagpur, > (India). > My interest lies in System Programming. I have taken courses like operating > system, computer networks etc. And I am familiar with multithreaded

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

Introduction and [PATCH V1]

2017-03-19 Thread Rohan Rajak
Hi, I am Rohan Rajak a 3rd year computer science student at IIT Kharagpur, (India). My interest lies in System Programming. I have taken courses like operating system, computer networks etc. And I am familiar with multithreaded and shell programming. I am looking forward to work in comprehensive t

GSoC 2017 Introduction: Netlink socket parsers

2017-03-18 Thread JingPiao Chen
Hello strace-developers: My name is JingPiao Chen. I'am a Computer Science sophomore from Guangdong Pharmaceutical University. I am interested in Netlink socket parsers suggested by Gabriel Laskar and Dmitry V. Levin. I am familiar with C, git, shell script, and gdb. My current work base on the co

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
n strace GSoC projects. > > > I wanted to add support of new ioctl commands from linux 4.9 - 4.11 as my > > introduction microproject, but I cannot understand, what kind of support > is > > needed. I have tested them on linux 4.9 and output is correct. > > I understa

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
Thanks for showing interest in strace GSoC projects. > I wanted to add support of new ioctl commands from linux 4.9 - 4.11 as my > introduction microproject, but I cannot understand, what kind of support is > needed. I have tested them on linux 4.9 and output is correct. I understand

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

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

Re: GSoC 2017 introduction

2017-03-12 Thread Eugene Syromyatnikov
On Sat, Mar 11, 2017 at 02:51:35PM +0300, Victor Krapivensky wrote: > Removed a trailing semicolon in a macro definition in tests/xstatx.c > and changed copyright holders of new files to "The strace developers". > > Please review this one. > > I've also found a possile buffer overflow bug in unwi

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 2017 introduction

2017-03-11 Thread Victor Krapivensky
Removed a trailing semicolon in a macro definition in tests/xstatx.c and changed copyright holders of new files to "The strace developers". Please review this one. I've also found a possile buffer overflow bug in unwind.c. Attaching a separate patch. On 03/10/2017 09:59 PM, Victor Krapivensky

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 2017 introduction

2017-03-10 Thread Victor Krapivensky
On 03/10/2017 04:36 AM, Dmitry V. Levin wrote: This cannot be correct. OK, removed it for now, and fixed all the issues you mentioned. I've also added a test, so please review. I've also stumbled upon a wrong comment in util.c. Attaching a separate patch for it. This is wrong, the type of n

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 2017 introduction

2017-03-09 Thread Dmitry V. Levin
On Fri, Mar 10, 2017 at 01:55:13AM +0300, Victor Krapivensky wrote: > From e8754de2791ddb6c79fd51a49c83582c9d9a01d7 Mon Sep 17 00:00:00 2001 > From: Victor Krapivensky > Date: Thu, 9 Mar 2017 20:26:14 +0300 > Subject: [PATCH v2] Add support for statx syscall I've given a very cursory look at this

Re: GSoC 2017 introduction

2017-03-09 Thread Victor Krapivensky
On 03/09/2017 10:24 PM, Eugene Syromyatnikov wrote: PS. Btw, by a quick look at the patch (haven't reviewed it yet), I can say that you at least forgot to wire up i386 arch [2], improperly indented SEN(statx) and most probably would have problems with struct statx name clash once glibc decided to

Re: GSoC 2017 introduction

2017-03-09 Thread Eugene Syromyatnikov
On Thu, Mar 9, 2017 at 5:44 PM, Victor Krapivensky wrote: > I would like to implement the parser for statx. Here is my current > attempt (no tests yet). > I've spotted the tests/statx.sh script. Unfortunately, due to that > tests/init.sh expects the caller name to end with ".test", it just > endle

Re: GSoC 2017 introduction

2017-03-09 Thread Victor Krapivensky
I would like to implement the parser for statx. Here is my current attempt (no tests yet). I've spotted the tests/statx.sh script. Unfortunately, due to that tests/init.sh expects the caller name to end with ".test", it just endlessly runs itself. What is it supposed to do? Also, how do I get sysc

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: Introduction

2017-03-07 Thread Rishi Bhatt
The output we see when we run lets say strace -e trace=open which will list all the open syscalls performed in the program. Now as per README-linux-ptrace (if i interpreted it correctly) when tracee is ptrace-stop the necessary information which we are getting as output is extracted by ptrace(PTRA

Re: GSoC 2017 introduction

2017-03-06 Thread Dmitry V. Levin
Hi Victor, On Sun, Mar 05, 2017 at 06:31:31PM +0300, Victor Krapivensky wrote: > Hi everybody! My name is Victor Krapivensky and I am a first-year > student at MIPT. > > I want to implement Lua-scriptable advanced syscall tampering for > strace. > > I am quite fluent in C, have an interest in sy

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: Introduction

2017-03-06 Thread Rishi Bhatt
Thanks, It helped me to where to look for answers i got a better idea now how a -e trace=option works,And i see many *.c files which have these SYS_FUNC() in them what are these files for? Thanks, Rishi On Sat, Mar 4, 2017 at 10:58 PM, Eugene Syromyatnikov wrote: > On Sat, Mar 4, 2017 at 5:15 P

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

GSoC 2017 introduction

2017-03-05 Thread Victor Krapivensky
Hi everybody! My name is Victor Krapivensky and I am a first-year student at MIPT. I want to implement Lua-scriptable advanced syscall tampering for strace. I am quite fluent in C, have an interest in system programming and debugging, and have good understanding of how Lua C API works. I have pr

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

Re: Introduction

2017-03-04 Thread Eugene Syromyatnikov
On Sat, Mar 4, 2017 at 5:15 PM, Rishi Bhatt wrote: > Thanks ldv, > I have read the man pages and got basic idea about strace.Now where should i > start understanding the code?The codebase is so big i dont know where to > start. The core is strace.c and syscall.c (mostly). Take a look at some simpl

Re: Introduction

2017-03-04 Thread Rishi Bhatt
Thanks ldv, I have read the man pages and got basic idea about strace.Now where should i start understanding the code?The codebase is so big i dont know where to start. On Sat, Mar 4, 2017 at 4:25 AM, Dmitry V. Levin wrote: > Hi, > > On Fri, Mar 03, 2017 at 11:55:33PM +0530, Rishi Bhatt wrote: >

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

Re: Introduction

2017-03-03 Thread Dmitry V. Levin
Hi, On Fri, Mar 03, 2017 at 11:55:33PM +0530, Rishi Bhatt wrote: > Hi ldv, > thanks for the reply i have build the strace source-code and when i > was building it it skipped 50 test cases. So do you know why that > happened? or is it the matter that i should look into? Why skipped or why 50? A

Re: Introduction

2017-03-03 Thread Rishi Bhatt
Hi ldv, thanks for the reply i have build the strace source-code and when i was building it it skipped 50 test cases. So do you know why that happened? or is it the matter that i should look into? And can you guide me where should i start to know about -e trace=class? Thanks Rishi. On 3/1/17, D

Re: Introduction

2017-03-01 Thread Dmitry V. Levin
Hi, On Tue, Feb 28, 2017 at 11:32:12PM +0530, Sumit Sardana wrote: > Hi everyone > > Congratulation to Strace on getting selected again as a mentoring > organization for GSoC 2017! > > I'm Sumit Sardana and doing under-graduation in Computer Science & > Engineering from Vellore Institute Of Tech

Introduction

2017-02-28 Thread Sumit Sardana
Hi everyone Congratulation to Strace on getting selected again as a mentoring organization for GSoC 2017! I'm Sumit Sardana and doing under-graduation in Computer Science & Engineering from Vellore Institute Of Technology, Vellore, India. I have knowledge of C,C++,git and shell programming(basi

[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

  1   2   >