All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Ekkehard Schmoll <eggi.innovations@gmail.com>
To: wei.liu2@citrix.com
Cc: xen-devel@lists.xenproject.org
Subject: [GSoC] GSoC Introduction : Fuzzing Xen hypercall interface
Date: Sun, 12 Mar 2017 21:48:11 +0100	[thread overview]
Message-ID: <2C3140B8-9B96-44F8-A4EA-CDBC07479379@gmail.com> (raw)

Hi,

I’m interested in the “Fuzzing Xen hypercall interface” project so I just wanted to introduce myself:

I’m a third-year undergraduate CS student at Jacobs University in Bremen, Germany. It’s a rather small university and rather young but quite successful in the national rankings (*brag*). 

Last semester I spent as part of an exchange program at CMU where I took the sort of notorious 15-410 Operating Systems course where you have to implement a kernel from scratch in 6 weeks. There the professor (amazing guy) mentioned/promoted GSoC quite a couple of times, and this seems like a really cool project to work on.

From the course I have quite a substantial amount of experience in C and ASM on x86, of the GCC toolchain and obviously of kernel programming. I don’t really have any experience with fuzzing yet, but I’m sure I’ll figure that out.

I’d appreciate it if you could point me to some small patches I could work on to get going (sorry if I missed the link to it).

Also any other comments are of course welcome.

Felix
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-03-12 20:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 20:48 Felix Ekkehard Schmoll [this message]
2017-03-13 11:14 ` [GSoC] GSoC Introduction : Fuzzing Xen hypercall interface Wei Liu
2017-03-16 15:53   ` Felix Schmoll
2017-03-16 16:27     ` Wei Liu
     [not found]       ` <CAK1m5j4UbGV9JZiXJ2Lo3=ztrgsCsFg7Vp--dAHfgOert7KkMw@mail.gmail.com>
     [not found]         ` <20170320161847.kic6b524lodgr25u@citrix.com>
2017-03-20 16:47           ` Felix Schmoll
2017-03-21 12:24             ` Wei Liu
     [not found]         ` <20170321161324.hmsnybth3ktjbzpk@citrix.com>
     [not found]           ` <20170321161442.tpjjtecv6qmsgmev@citrix.com>
2017-03-22  8:47             ` Felix Schmoll
2017-03-22  8:52               ` Wei Liu
2017-03-22  9:54                 ` Felix Schmoll
2017-03-22 11:21                   ` Wei Liu
2017-03-23  7:18                     ` Felix Schmoll
2017-03-23  7:19                       ` Felix Schmoll
2017-03-24  7:34                     ` Felix Schmoll
2017-03-24 12:13                       ` Juergen Gross
2017-03-24 12:56                       ` Wei Liu
2017-03-26 11:33                         ` Felix Schmoll
2017-03-26 13:04                           ` Wei Liu
2017-03-27 13:07                             ` Felix Schmoll
2017-03-28  9:21                               ` Lars Kurth
2017-03-28 11:54                                 ` Wei Liu
2017-03-29  5:52                                   ` Felix Schmoll
2017-03-29 10:41                                     ` Wei Liu
2017-03-29 14:24                                       ` Felix Schmoll
2017-03-29 15:54                                         ` Wei Liu
2017-03-29 18:19                                           ` Felix Schmoll

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2C3140B8-9B96-44F8-A4EA-CDBC07479379@gmail.com \
    --to=eggi.innovations@gmail.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.