Hi Amit,
On Fri, Mar 10, 2017 at 01:19:07AM +0530, Amit Rege wrote:
> Hey, My name is Amit. I'm a CS student interested in systems programming.
> My programming background is mostly in C++, Java and Python.
> I have read the replies on the threads started by other applicants so I
> just wanted to
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
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
Hey, My name is Amit. I'm a CS student interested in systems programming.
My programming background is mostly in C++, Java and Python.
I have read the replies on the threads started by other applicants so I
just wanted to introduce myself.
I was interested in the project "Advanced syscall tampering
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
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
