strace-devel

Introduction

[Rajul S. <raj...@gm...>]

Hi all,

My name in Rajul, and I am a final year undergraduate student at the Indian
Institute of Technology Kharagpur. I wish to participate in
Google Summer of Code 2014, and while going through the list of
organisations, I came across "*strace*". I am proficient with programming
languages C/C++, Python, Java, Groovy, Ruby. I am very interested in the
fields of System Programming, Computer Organisation and Architecture and
Operating Systems.

I have always been interested in programming and in the past I have
participated in Google Summer of Code 2012, with the organisation
Network Time Foundation,working on the project "improving the
Logging/Debugging System of Network Time Protocol Software". I have also
interned in the Global Technology division of Barclays, during the summers
of 2013, working with the Market Risk IT team. Besides I have worked on a
few Research projects in the fields
of Computational Finance, Complex Networks, and Computational Chemistry. I
am currently working on my Thesis project in the field
of Computational Sciences on a project titled "Network Analysis
of Chemical Reactions". I have had courses in the fields of Programming and
Data Structures, Complex Networks, Distributed Systems,
Algorithms, Operations Research in the past.

I have gone through the list of project ideas and I found most of the
project ideas very interesting. Although I find all the projects listed
worth a while, I am particularly interested in the "*Reliable
multiarchitecture support*" and "*Advanced and improved absolute paths
decoding*" projects. I suppose that my programming background is suitable
for these projects.

I shall be grateful if anyone can help me and give me reference to the
documentation that I may use to get myself started with the code-base and
also shed some light on how I can go about making a successful proposal.

Thanks!!

Best Regards,
Rajul

-- 
Rajul
Final year Undergraduate Student,
Indian Institute of Technology Kharagpur

Introduction

[Alangi D. <ala...@gm...>]

Hello Strace Members,
                    I am called Alangi Derick Ndimnain, i am from
Cameroon and i recently founded this organisation called Strace that i
like to work with this summer of code 2014. I am a Computer
Engineering Student in the University of Buea, Cameroon. My interest
to work with this organisation is because we studied a course in our
university this year called Systems programming and i did very well in
the course in both the CA and the Exams.
   Statistics
   - CA - Score [28/30]
   - Exams - Score [unknown]
The statistics for the Exams is yet unknown because it has not yet been marked.

I like system programming and fortunately too, i am program in the C
language and to finish all these, i want to work for an organisation
to make sure that i put in practice the ideas that i learnt in school
for the use of all in the world and i will like to use this
opportunity to make a difference in Strace.
                Thanks for your understanding
                               Alangi Derick

                               Cheers!!!

Re: Introduction

[Philippe O. <pom...@ne...>]

On Sun, Mar 9, 2014 at 3:30 PM, Alangi Derick <ala...@gm...> wrote:
> Hello Strace Members,
>                     I am called Alangi Derick Ndimnain, i am from
> Cameroon and i recently founded this organisation called Strace that i
> like to work with this summer of code 2014. I am a Computer
> Engineering Student in the University of Buea, Cameroon. My interest
> to work with this organisation is because we studied a course in our
> university this year called Systems programming and i did very well in
> the course in both the CA and the Exams.
>    Statistics
>    - CA - Score [28/30]
>    - Exams - Score [unknown]
> The statistics for the Exams is yet unknown because it has not yet been marked.
>
> I like system programming and fortunately too, i am program in the C
> language and to finish all these, i want to work for an organisation
> to make sure that i put in practice the ideas that i learnt in school
> for the use of all in the world and i will like to use this
> opportunity to make a difference in Strace.
>                 Thanks for your understanding
>                                Alangi Derick
>
>                                Cheers!!!

Hi Alangi Derick:
welcome to strace!
Do you go by Alangi or Alangi Derick?
Is there a specific project idea that you find interesting?

-- 
Philippe Ombredanne

Re: Introduction

[Alangi D. <ala...@gm...>]

Well i am still looking at the projects and if i find any that
interests me, then i will make sure i inform you immediately. I go by
Alangi Derick.

On Sun, Mar 9, 2014 at 5:28 PM, Philippe Ombredanne
<pom...@ne...> wrote:
> On Sun, Mar 9, 2014 at 3:30 PM, Alangi Derick <ala...@gm...> wrote:
>> Hello Strace Members,
>>                     I am called Alangi Derick Ndimnain, i am from
>> Cameroon and i recently founded this organisation called Strace that i
>> like to work with this summer of code 2014. I am a Computer
>> Engineering Student in the University of Buea, Cameroon. My interest
>> to work with this organisation is because we studied a course in our
>> university this year called Systems programming and i did very well in
>> the course in both the CA and the Exams.
>>    Statistics
>>    - CA - Score [28/30]
>>    - Exams - Score [unknown]
>> The statistics for the Exams is yet unknown because it has not yet been marked.
>>
>> I like system programming and fortunately too, i am program in the C
>> language and to finish all these, i want to work for an organisation
>> to make sure that i put in practice the ideas that i learnt in school
>> for the use of all in the world and i will like to use this
>> opportunity to make a difference in Strace.
>>                 Thanks for your understanding
>>                                Alangi Derick
>>
>>                                Cheers!!!
>
> Hi Alangi Derick:
> welcome to strace!
> Do you go by Alangi or Alangi Derick?
> Is there a specific project idea that you find interesting?
>
> --
> Philippe Ombredanne
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Strace-devel mailing list
> Str...@li...
> https://lists.sourceforge.net/lists/listinfo/strace-devel

Introduction

[Alangi D. <ala...@gm...>]

Hello,
    I am Alangi Derick, a student from the University of Buea, Cameroon. I
am a third year undergraduate student doing Software Engineering. I was
looking at organisations to contribute code in using the C programming
language. Thank God i have found one which is Strace. What i want now is
for the members of strace to guide me with some link in order for me to
understand the community and what they do so that i can get started at one
to work on small mini project and contribute code and also propose ideas. I
will also like to know the lead developers in the community and if the
Organisation has an irc channel for communication. I want to really develop
and work with system calls so as to make linux a better one and process in
linux too. I want to further my knowledge in the course we did in school
called System Programming which talked about system call. I want to be able
to write my own system call and see how it works in a linux system. I will
be waiting for a reply to this mail.
             Thanks

Re: Introduction

[Mike F. <va...@ge...>]

On 17 Feb 2015 11:16, Alangi Derick wrote:
> for the members of strace to guide me with some link in order for me to
> understand the community and what they do so that i can get started at one

pretty simple:
 - there's git where all the code lives
 - there's this mailing list where all discussion/patches/reports get sent

so once you know how to use git and e-mail, you've got everything ;)
-mike

Re: Introduction

[Philippe O. <pom...@ne...>]

On Wed, Feb 18, 2015 at 9:05 PM, Mike Frysinger <va...@ge...> wrote:
> On 17 Feb 2015 11:16, Alangi Derick wrote:
>> for the members of strace to guide me with some link in order for me to
>> understand the community and what they do so that i can get started at one
>
> pretty simple:
>  - there's git where all the code lives
>  - there's this mailing list where all discussion/patches/reports get sent
>
> so once you know how to use git and e-mail, you've got everything ;)

Mike: That's a pretty darn good and short intro. I like it.
Alangi: Add a pinch of C to it and you will be on a roll. This is a fun project!

-- 
Cordially
Philippe Ombredanne

Introduction

[Sumit S. <sar...@gm...>]

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(basic). Working with
system calls and process states sounds interesting. I wanted to contribute
to the community as part of GSoC 2017.

Interested in working on :

**Netlink socket parsers *Suggested by: Gabriel Laskar, Dmitry V. Levin *

Can anybody please help me get started.

Being a college undergrad : Super excited to work on the project with a
motto to learn and contribute as much as I can.

Re: Introduction

[Dmitry V. L. <ld...@al...>]

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 Technology, Vellore, India.
> 
> I have knowledge of C,C++,git and  shell programming(basic). Working with
> system calls and process states sounds interesting. I wanted to contribute
> to the community as part of GSoC 2017.
> 
> Interested in working on :
> 
> **Netlink socket parsers *Suggested by: Gabriel Laskar, Dmitry V. Levin *
> 
> Can anybody please help me get started.

You can start with
https://sourceforge.net/p/strace/wiki/GoogleSummerOfCode2017/
that contains information about strace participation in the GSoC 2017.

There is a short guide for new contributors at
https://sourceforge.net/p/strace/wiki/Guide%20for%20new%20contributors/

You can find some information about contribution requirements at
https://github.com/strace/strace/blob/master/README-hacking
Other README* files also worth a look.

There is an archive of this mailing list at
https://sourceforge.net/p/strace/mailman/strace-devel/
that contains lots of information.


-- 
ldv

Re: Introduction

[Rishi B. <bha...@gm...>]

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, Dmitry V. Levin <ld...@al...> wrote:
> 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 Technology, Vellore, India.
>>
>> I have knowledge of C,C++,git and  shell programming(basic). Working with
>> system calls and process states sounds interesting. I wanted to
>> contribute
>> to the community as part of GSoC 2017.
>>
>> Interested in working on :
>>
>> **Netlink socket parsers *Suggested by: Gabriel Laskar, Dmitry V. Levin *
>>
>> Can anybody please help me get started.
>
> You can start with
> https://sourceforge.net/p/strace/wiki/GoogleSummerOfCode2017/
> that contains information about strace participation in the GSoC 2017.
>
> There is a short guide for new contributors at
> https://sourceforge.net/p/strace/wiki/Guide%20for%20new%20contributors/
>
> You can find some information about contribution requirements at
> https://github.com/strace/strace/blob/master/README-hacking
> Other README* files also worth a look.
>
> There is an archive of this mailing list at
> https://sourceforge.net/p/strace/mailman/strace-devel/
> that contains lots of information.
>
>
> --
> ldv
>

Re: Introduction

[Dmitry V. L. <ld...@al...>]

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 test can be skipped if
- it is not applicable for the architecture being tested, for example,
  the test is for a syscall that is not inplemented for this architecture;
- the test framework doesn't support the test, for example, a kernel
  module is not loaded, or the filesystem is not capable, etc.

Currently there are two architectures where exactly 50 tests are skipped:
- native x86_64;
- native sparc64.

I bet sparc64 is not your case, so you must be running the test suite
natively on x86_64.

> And can you guide me where should i start to know about -e trace=class?

I think the best is to start with reading the manual page, then look
at the code to understand how it's implemented.  As soon as you've
understood the implementation, it's easy to extend.


-- 
ldv

Re: Introduction

[Rishi B. <bha...@gm...>]

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 <ld...@al...> wrote:

> 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 test can be skipped if
> - it is not applicable for the architecture being tested, for example,
>   the test is for a syscall that is not inplemented for this architecture;
> - the test framework doesn't support the test, for example, a kernel
>   module is not loaded, or the filesystem is not capable, etc.
>
> Currently there are two architectures where exactly 50 tests are skipped:
> - native x86_64;
> - native sparc64.
>
> I bet sparc64 is not your case, so you must be running the test suite
> natively on x86_64.
>
> > And can you guide me where should i start to know about -e trace=class?
>
> I think the best is to start with reading the manual page, then look
> at the code to understand how it's implemented.  As soon as you've
> understood the implementation, it's easy to extend.
>
>

> --
> ldv
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Strace-devel mailing list
> Str...@li...
> https://lists.sourceforge.net/lists/listinfo/strace-devel
>
>

Re: Introduction

[Eugene S. <ev...@gm...>]

On Sat, Mar 4, 2017 at 5:15 PM, Rishi Bhatt <bha...@gm...> 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
simple (umask.c, readahead.c, mount.c) and not so simple (time.c,
ioctl.c, net.c, signal.c, ipc.c) decoders. You can look at some tests
then, like umask, or aio, or sendmmsg, or btrfs. util.c contains
various utility functions, defs.h contains various utility macros and
inlines. linux directory contains various (mostly
architecture-specific) system definitions which are preferred to be
part of strace codebase. linux/*/syscallent.h contains wirings for
syscalls. xlat directory contains sources for generation of symbolic
constant headers.

> On Sat, Mar 4, 2017 at 4:25 AM, Dmitry V. Levin <ld...@al...> wrote:
>>
>> 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 test can be skipped if
>> - it is not applicable for the architecture being tested, for example,
>>   the test is for a syscall that is not inplemented for this architecture;
>> - the test framework doesn't support the test, for example, a kernel
>>   module is not loaded, or the filesystem is not capable, etc.
>>
>> Currently there are two architectures where exactly 50 tests are skipped:
>> - native x86_64;
>> - native sparc64.
>>
>> I bet sparc64 is not your case, so you must be running the test suite
>> natively on x86_64.
>>
>> > And can you guide me where should i start to know about -e trace=class?
>>
>> I think the best is to start with reading the manual page, then look
>> at the code to understand how it's implemented.  As soon as you've
>> understood the implementation, it's easy to extend.
>>
>
>>
>> --
>> ldv
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Strace-devel mailing list
>> Str...@li...
>> https://lists.sourceforge.net/lists/listinfo/strace-devel
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Strace-devel mailing list
> Str...@li...
> https://lists.sourceforge.net/lists/listinfo/strace-devel
>



-- 
Eugene Syromyatnikov
mailto:ev...@gm...
xmpp:esyr@jabber.{ru|org}

Re: Introduction

[Rishi B. <bha...@gm...>]

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 <ev...@gm...>
wrote:

> On Sat, Mar 4, 2017 at 5:15 PM, Rishi Bhatt <bha...@gm...>
> 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
> simple (umask.c, readahead.c, mount.c) and not so simple (time.c,
> ioctl.c, net.c, signal.c, ipc.c) decoders. You can look at some tests
> then, like umask, or aio, or sendmmsg, or btrfs. util.c contains
> various utility functions, defs.h contains various utility macros and
> inlines. linux directory contains various (mostly
> architecture-specific) system definitions which are preferred to be
> part of strace codebase. linux/*/syscallent.h contains wirings for
> syscalls. xlat directory contains sources for generation of symbolic
> constant headers.
>
> > On Sat, Mar 4, 2017 at 4:25 AM, Dmitry V. Levin <ld...@al...>
> wrote:
> >>
> >> 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 test can be skipped if
> >> - it is not applicable for the architecture being tested, for example,
> >>   the test is for a syscall that is not inplemented for this
> architecture;
> >> - the test framework doesn't support the test, for example, a kernel
> >>   module is not loaded, or the filesystem is not capable, etc.
> >>
> >> Currently there are two architectures where exactly 50 tests are
> skipped:
> >> - native x86_64;
> >> - native sparc64.
> >>
> >> I bet sparc64 is not your case, so you must be running the test suite
> >> natively on x86_64.
> >>
> >> > And can you guide me where should i start to know about -e
> trace=class?
> >>
> >> I think the best is to start with reading the manual page, then look
> >> at the code to understand how it's implemented.  As soon as you've
> >> understood the implementation, it's easy to extend.
> >>
> >
> >>
> >> --
> >> ldv
> >>
> >>
> >> ------------------------------------------------------------
> ------------------
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> >> _______________________________________________
> >> Strace-devel mailing list
> >> Str...@li...
> >> https://lists.sourceforge.net/lists/listinfo/strace-devel
> >>
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Strace-devel mailing list
> > Str...@li...
> > https://lists.sourceforge.net/lists/listinfo/strace-devel
> >
>
>
>
> --
> Eugene Syromyatnikov
> mailto:ev...@gm...
> xmpp:esyr@jabber.{ru|org}
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Strace-devel mailing list
> Str...@li...
> https://lists.sourceforge.net/lists/listinfo/strace-devel
>

Re: Introduction

[Rishi B. <bha...@gm...>]

The output we see when we run lets say strace -e trace=open <program> 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(PTRACE_*,pid,...,...)  and this extracted information
is somehow directed towards its specific decoder in this example open.c and
then the decoders in the open.c are responsible for printing out the
information.Am i correct with the flow?

On Mon, Mar 6, 2017 at 8:32 PM, Rishi Bhatt <bha...@gm...>
wrote:

> 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 <ev...@gm...>
> wrote:
>
>> On Sat, Mar 4, 2017 at 5:15 PM, Rishi Bhatt <bha...@gm...>
>> 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
>> simple (umask.c, readahead.c, mount.c) and not so simple (time.c,
>> ioctl.c, net.c, signal.c, ipc.c) decoders. You can look at some tests
>> then, like umask, or aio, or sendmmsg, or btrfs. util.c contains
>> various utility functions, defs.h contains various utility macros and
>> inlines. linux directory contains various (mostly
>> architecture-specific) system definitions which are preferred to be
>> part of strace codebase. linux/*/syscallent.h contains wirings for
>> syscalls. xlat directory contains sources for generation of symbolic
>> constant headers.
>>
>> > On Sat, Mar 4, 2017 at 4:25 AM, Dmitry V. Levin <ld...@al...>
>> wrote:
>> >>
>> >> 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 test can be skipped if
>> >> - it is not applicable for the architecture being tested, for example,
>> >>   the test is for a syscall that is not inplemented for this
>> architecture;
>> >> - the test framework doesn't support the test, for example, a kernel
>> >>   module is not loaded, or the filesystem is not capable, etc.
>> >>
>> >> Currently there are two architectures where exactly 50 tests are
>> skipped:
>> >> - native x86_64;
>> >> - native sparc64.
>> >>
>> >> I bet sparc64 is not your case, so you must be running the test suite
>> >> natively on x86_64.
>> >>
>> >> > And can you guide me where should i start to know about -e
>> trace=class?
>> >>
>> >> I think the best is to start with reading the manual page, then look
>> >> at the code to understand how it's implemented.  As soon as you've
>> >> understood the implementation, it's easy to extend.
>> >>
>> >
>> >>
>> >> --
>> >> ldv
>> >>
>> >>
>> >> ------------------------------------------------------------
>> ------------------
>> >> Check out the vibrant tech community on one of the world's most
>> >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> >> _______________________________________________
>> >> Strace-devel mailing list
>> >> Str...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/strace-devel
>> >>
>> >
>> >
>> > ------------------------------------------------------------
>> ------------------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> > _______________________________________________
>> > Strace-devel mailing list
>> > Str...@li...
>> > https://lists.sourceforge.net/lists/listinfo/strace-devel
>> >
>>
>>
>>
>> --
>> Eugene Syromyatnikov
>> mailto:ev...@gm...
>> xmpp:esyr@jabber.{ru|org}
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Strace-devel mailing list
>> Str...@li...
>> https://lists.sourceforge.net/lists/listinfo/strace-devel
>>
>
>

Introduction

[Manvendra S. <man...@gm...>]

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'm Super excited to work on the project with a
motto to learn and contribute as much as I can.

Re: Introduction

[Eugene S. <ev...@gm...>]

On Sat, Nov 18, 2017 at 8:38 PM, Manvendra Singh
<man...@gm...> 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 community.
> Can anybody please help me get started.

Thank you for showing interest in strace.

Please take a look at [1], [2], and [3] as starting points. If you have
any specific questions, don't hesitate to ask.

[1] https://sourceforge.net/p/strace/wiki/Guide%20for%20new%20contributors/
[2] https://sourceforge.net/p/strace/wiki/Microprojects/
[3] https://sourceforge.net/p/strace/wiki/FeatureRequests/

-- 
Eugene Syromyatnikov
mailto:ev...@gm...
xmpp:esyr@jabber.{ru|org}

Introduction

[gou4shi1 <ad...@go...>]

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.

Introduction

[Harsha S. <har...@gm...>]

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).
Strace is one of my favorite tools in linux and want to contribute to
the community.
 I have looked into the mail archives about getting started and
submitted two small patches. I have tried to understand the test
infrastructure and will like to add some tests or fix some of the
existing tests.
It'll be great if someone can suggest either some tests or any other
small bug-fix that I can work upon.
Thanks :)

Regards,
Harsha Sharma

[GSOC] Introduction

[Fabien S. <fab...@ep...>]

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 parsers*. It consists to do a similar
interface as ioctl to netlink.  Netlink is a standard sockets-based
interface to transfer information between kernel and user-space processes.
You can find it in applications such as iproute, iptables...

Cheers,

--
Fabien Siron

Re: Introduction

[JingPiao C. <che...@gm...>]

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-kernel
> (project nftables - Network filtration tool).
> Strace is one of my favorite tools in linux and want to contribute to
> the community.
>  I have looked into the mail archives about getting started and
> submitted two small patches. I have tried to understand the test
> infrastructure and will like to add some tests or fix some of the
> existing tests.
> It'll be great if someone can suggest either some tests or any other
> small bug-fix that I can work upon.
> Thanks :)

I think write netlink socket parser is suited for you. This is a GSoC 2016
and 2017 project. The part of netfilter has not implemented yet.
I working on it, but recent I am busy. If you are interested in it, please
tell me.

More information:

strace GSoC 2017 netlink socket parsers:
https://ppiao.github.io/2017/08/22/strace-gsoc-2017-netlink-socket-parser.html

My current work of netfilter parser:
(Need to fix.)
https://github.com/ppiao/strace

--
Chen Jingpiao

Re: Introduction

[Harsha S. <har...@gm...>]

On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen <che...@gm...> 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
>> and parsers and currently working as outreachy intern in Linux-kernel
>> (project nftables - Network filtration tool).
>> Strace is one of my favorite tools in linux and want to contribute to
>> the community.
>>  I have looked into the mail archives about getting started and
>> submitted two small patches. I have tried to understand the test
>> infrastructure and will like to add some tests or fix some of the
>> existing tests.
>> It'll be great if someone can suggest either some tests or any other
>> small bug-fix that I can work upon.
>> Thanks :)
>
> I think write netlink socket parser is suited for you. This is a GSoC 2016
> and 2017 project. The part of netfilter has not implemented yet.
> I working on it, but recent I am busy. If you are interested in it, please
> tell me.
>
Yes, definitely. I'm interested.
How should I start with the project ? (Any guidance will be
appreciated, meanwhile I'll try to go through your code in strace.)
Can you assign me a small task in the project ?
Thanks for your time. :')

> More information:
>
> strace GSoC 2017 netlink socket parsers:
> https://ppiao.github.io/2017/08/22/strace-gsoc-2017-netlink-socket-parser.html
>
> My current work of netfilter parser:
> (Need to fix.)
> https://github.com/ppiao/strace
>
> --
> Chen Jingpiao
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Strace-devel mailing list
> Str...@li...
> https://lists.sourceforge.net/lists/listinfo/strace-devel

Re: Introduction

[Chen J. <che...@gm...>]

On 12/25 10:26, Harsha Sharma wrote:
> On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen <che...@gm...> 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
> >> and parsers and currently working as outreachy intern in Linux-kernel
> >> (project nftables - Network filtration tool).
> >> Strace is one of my favorite tools in linux and want to contribute to
> >> the community.
> >>  I have looked into the mail archives about getting started and
> >> submitted two small patches. I have tried to understand the test
> >> infrastructure and will like to add some tests or fix some of the
> >> existing tests.
> >> It'll be great if someone can suggest either some tests or any other
> >> small bug-fix that I can work upon.
> >> Thanks :)
> >
> > I think write netlink socket parser is suited for you. This is a GSoC 2016
> > and 2017 project. The part of netfilter has not implemented yet.
> > I working on it, but recent I am busy. If you are interested in it, please
> > tell me.
> >
> Yes, definitely. I'm interested.
> How should I start with the project ? (Any guidance will be
> appreciated, meanwhile I'll try to go through your code in strace.)
> Can you assign me a small task in the project ?
> Thanks for your time. :')

300d9f1f: Further decode some attributes.
37dfe8c7: Implement a small protocol.

You can read these commits to get some idea. I recommend you to decode libudev
netlink header (struct udev_monitor_netlink_header).

systemd/src/libudev/libudev-monitor.c: 76
struct udev_monitor_netlink_header {
        /* "libudev" prefix to distinguish libudev and kernel messages */
        char prefix[8];
        /*
         * magic to protect against daemon <-> library message format mismatch
         * used in the kernel from socket filter rules; needs to be stored in network order
         */
        unsigned int magic;
        /* total length of header structure known to the sender */
        unsigned int header_size;
        /* properties string buffer */
        unsigned int properties_off;
        unsigned int properties_len;
        /*
         * hashes of primary device properties strings, to let libudev subscribers
         * use in-kernel socket filters; values need to be stored in network order
         */
        unsigned int filter_subsystem_hash;
        unsigned int filter_devtype_hash;
        unsigned int filter_tag_bloom_hi;
        unsigned int filter_tag_bloom_lo;
};

Netlink overview and its strace parsers:
http://blog.saruta.eu/netlink_strace.html

> 
> > More information:
> >
> > strace GSoC 2017 netlink socket parsers:
> > https://ppiao.github.io/2017/08/22/strace-gsoc-2017-netlink-socket-parser.html
> >
> > My current work of netfilter parser:
> > (Need to fix.)
> > https://github.com/ppiao/strace
> >

--
Chen Jingpiao

Re: Introduction

[Harsha S. <har...@gm...>]

On Tue, Dec 26, 2017 at 9:49 AM, Chen Jingpiao <che...@gm...> wrote:
> On 12/25 10:26, Harsha Sharma wrote:
>> On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen <che...@gm...> 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
>> >> and parsers and currently working as outreachy intern in Linux-kernel
>> >> (project nftables - Network filtration tool).
>> >> Strace is one of my favorite tools in linux and want to contribute to
>> >> the community.
>> >>  I have looked into the mail archives about getting started and
>> >> submitted two small patches. I have tried to understand the test
>> >> infrastructure and will like to add some tests or fix some of the
>> >> existing tests.
>> >> It'll be great if someone can suggest either some tests or any other
>> >> small bug-fix that I can work upon.
>> >> Thanks :)
>> >
>> > I think write netlink socket parser is suited for you. This is a GSoC 2016
>> > and 2017 project. The part of netfilter has not implemented yet.
>> > I working on it, but recent I am busy. If you are interested in it, please
>> > tell me.
>> >
>> Yes, definitely. I'm interested.
>> How should I start with the project ? (Any guidance will be
>> appreciated, meanwhile I'll try to go through your code in strace.)
>> Can you assign me a small task in the project ?
>> Thanks for your time. :')
>
> 300d9f1f: Further decode some attributes.
> 37dfe8c7: Implement a small protocol.
>
> You can read these commits to get some idea.

I'm unable to find the header file for kobject_uevent_types (like
rtnetlink.h and selinux_netlink.h in case of route and selinux ).
I'm approaching in the way similar to netlink_route and
netlink_selinux, is this correct ?

> I recommend you to decode libudev
> netlink header (struct udev_monitor_netlink_header).
>
> systemd/src/libudev/libudev-monitor.c: 76
> struct udev_monitor_netlink_header {
>         /* "libudev" prefix to distinguish libudev and kernel messages */
>         char prefix[8];
>         /*
>          * magic to protect against daemon <-> library message format mismatch
>          * used in the kernel from socket filter rules; needs to be stored in network order
>          */
>         unsigned int magic;
>         /* total length of header structure known to the sender */
>         unsigned int header_size;
>         /* properties string buffer */
>         unsigned int properties_off;
>         unsigned int properties_len;
>         /*
>          * hashes of primary device properties strings, to let libudev subscribers
>          * use in-kernel socket filters; values need to be stored in network order
>          */
>         unsigned int filter_subsystem_hash;
>         unsigned int filter_devtype_hash;
>         unsigned int filter_tag_bloom_hi;
>         unsigned int filter_tag_bloom_lo;
> };

./tests/netlink_kobject_uevent
sendto(3, "\0\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37",
32, MSG_DONTWAIT, NULL, 0) = -1 ECONNREFUSED (Connection refused)
sendto(3, "=\0\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36"...,
33, MSG_DONTWAIT, NULL, 0) = -1 ECONNREFUSED (Connection refused)
+++ exited with 0 +++

This string "\0\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"
 needs to be parsed as prefix, magic, header_size, properties_off,
properties_len, and more ( from struct udev_monitor_netlink_header).
Is this correct, just want to make sure that I'm approaching in right
direction ?
Thanks for your time.

Regards,
Harsha Sharma

> Netlink overview and its strace parsers:
> http://blog.saruta.eu/netlink_strace.html
>
>>
>> > More information:
>> >
>> > strace GSoC 2017 netlink socket parsers:
>> > https://ppiao.github.io/2017/08/22/strace-gsoc-2017-netlink-socket-parser.html
>> >
>> > My current work of netfilter parser:
>> > (Need to fix.)
>> > https://github.com/ppiao/strace
>> >
>
> --
> Chen Jingpiao
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Strace-devel mailing list
> Str...@li...
> https://lists.sourceforge.net/lists/listinfo/strace-devel

Re: Introduction

[Chen J. <che...@gm...>]

On 12/26 10:53, Harsha Sharma wrote:
> On Tue, Dec 26, 2017 at 9:49 AM, Chen Jingpiao <che...@gm...>
wrote:
> > On 12/25 10:26, Harsha Sharma wrote:
> >> On Mon, Dec 25, 2017 at 6:51 PM, JingPiao Chen <che...@gm...>
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
> >> >> and parsers and currently working as outreachy intern in
Linux-kernel
> >> >> (project nftables - Network filtration tool).
> >> >> Strace is one of my favorite tools in linux and want to contribute
to
> >> >> the community.
> >> >>  I have looked into the mail archives about getting started and
> >> >> submitted two small patches. I have tried to understand the test
> >> >> infrastructure and will like to add some tests or fix some of the
> >> >> existing tests.
> >> >> It'll be great if someone can suggest either some tests or any other
> >> >> small bug-fix that I can work upon.
> >> >> Thanks :)
> >> >
> >> > I think write netlink socket parser is suited for you. This is a
GSoC 2016
> >> > and 2017 project. The part of netfilter has not implemented yet.
> >> > I working on it, but recent I am busy. If you are interested in it,
please
> >> > tell me.
> >> >
> >> Yes, definitely. I'm interested.
> >> How should I start with the project ? (Any guidance will be
> >> appreciated, meanwhile I'll try to go through your code in strace.)
> >> Can you assign me a small task in the project ?
> >> Thanks for your time. :')
> >
> > 300d9f1f: Further decode some attributes.
> > 37dfe8c7: Implement a small protocol.
> >
> > You can read these commits to get some idea.
>
> I'm unable to find the header file for kobject_uevent_types (like
> rtnetlink.h and selinux_netlink.h in case of route and selinux ).
> I'm approaching in the way similar to netlink_route and
> netlink_selinux, is this correct ?

NETLINK_KOBJECT_UEVENT netlink messages without a netlink message header.
You can search source code to see how to handle this.

$ git grep "NETLINK_KOBJECT_UEVENT"
netlink.c:      if (family == NETLINK_KOBJECT_UEVENT) {

If family == NETLINK_KOBJECT_UEVENT, we deocde NETLINK_KOBJECT_UEVENT
directly.

>
> > I recommend you to decode libudev
> > netlink header (struct udev_monitor_netlink_header).
> >
> > systemd/src/libudev/libudev-monitor.c: 76
> > struct udev_monitor_netlink_header {
> >         /* "libudev" prefix to distinguish libudev and kernel messages
*/
> >         char prefix[8];
> >         /*
> >          * magic to protect against daemon <-> library message format
mismatch
> >          * used in the kernel from socket filter rules; needs to be
stored in network order
> >          */
> >         unsigned int magic;
> >         /* total length of header structure known to the sender */
> >         unsigned int header_size;
> >         /* properties string buffer */
> >         unsigned int properties_off;
> >         unsigned int properties_len;
> >         /*
> >          * hashes of primary device properties strings, to let libudev
subscribers
> >          * use in-kernel socket filters; values need to be stored in
network order
> >          */
> >         unsigned int filter_subsystem_hash;
> >         unsigned int filter_devtype_hash;
> >         unsigned int filter_tag_bloom_hi;
> >         unsigned int filter_tag_bloom_lo;
> > };
>
> ./tests/netlink_kobject_uevent
> sendto(3,
"\0\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37",
> 32, MSG_DONTWAIT, NULL, 0) = -1 ECONNREFUSED (Connection refused)
> sendto(3,
"=\0\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36"...,
> 33, MSG_DONTWAIT, NULL, 0) = -1 ECONNREFUSED (Connection refused)
> +++ exited with 0 +++
>
> This string
"\0\1\2\3\4\5\6\7\10\t\n\v\f\r\16\17\20\21\22\23\24\25\26\27\30\31\32\33\34\35\36\37"
>  needs to be parsed as prefix, magic, header_size, properties_off,
> properties_len, and more ( from struct udev_monitor_netlink_header).
> Is this correct, just want to make sure that I'm approaching in right
> direction ?
> Thanks for your time.

If the prefix is "libudev", it contain struct udev_monitor_netlink_header.

You can read current strace output to get some idea.

$ strace -e%network udevadm monitor > /dev/null # Remove your mouse
$ strace -e%network udevadm monitor -u > /dev/null # Remove your mouse
$ strace -e%network udevadm monitor -k > /dev/null # Remove your mouse

>
> Regards,
> Harsha Sharma
>
> > Netlink overview and its strace parsers:
> > http://blog.saruta.eu/netlink_strace.html
> >
> >>
> >> > More information:
> >> >
> >> > strace GSoC 2017 netlink socket parsers:
> >> >
https://ppiao.github.io/2017/08/22/strace-gsoc-2017-netlink-socket-parser.html
> >> >
> >> > My current work of netfilter parser:
> >> > (Need to fix.)
> >> > https://github.com/ppiao/strace
> >> >
> >

--
Chen Jingpiao