From: Richard Henderson <richard.henderson@linaro.org>
To: Vishnu Dev <vishnudevtj@gmail.com>, qemu-devel@nongnu.org
Cc: agraf@suse.de, peter.maydell@linaro.org, alex.bennee@linaro.org
Subject: Re: [Qemu-devel] Implementing Memory Tag Extention - ARM
Date: Sun, 20 Jan 2019 07:50:44 +1100 [thread overview]
Message-ID: <5cad9e5e-853b-2ef7-d0d7-8b072d6277ef@linaro.org> (raw)
In-Reply-To: <CADCM7VHNg1y_bixYKZOaFnS5_Jgig-==tK_ZpT3jk8Q0aVsgFg@mail.gmail.com>
On 1/19/19 4:58 AM, Vishnu Dev wrote:
> Hello,
> I am a undergraduate Binary Exploitation enthusiast who would like to
> participate in GSoC with qemu on some security related project . While
> enquiring on IRC @agraf suggested a idea of implementing memory tag extension
> on ARM, this seems to be a good project . I have some experience reversing ARM
> binaries and exploitation on ARM architecture but have not done any open source
> contribution but I feel GSoC will be a great opportunity for me to begin and
> since I am really found of low level stuff, qemu seems to be a good
> organization to work with . also Qemu have helped me while working on ARM
> exploitation and Linux kernel Exploitation.
>
> Is this project feasible to implement as a GSoC project this year .
I have just posted an implementation of this extension.
http://lists.nongnu.org/archive/html/qemu-devel/2019-01/msg02599.html
r~
next prev parent reply other threads:[~2019-01-19 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 17:58 [Qemu-devel] Implementing Memory Tag Extention - ARM Vishnu Dev
2019-01-19 20:50 ` Richard Henderson [this message]
2019-01-20 7:12 ` Alexander Graf
2019-01-21 5:41 ` Vishnu Dev
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=5cad9e5e-853b-2ef7-d0d7-8b072d6277ef@linaro.org \
--to=richard.henderson@linaro.org \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vishnudevtj@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).