All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: lsf-pc@lists.linux-foundation.org,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [LSF/MM ATTEND] mm validation, hugepages
Date: Tue, 16 Feb 2016 12:44:03 -0500	[thread overview]
Message-ID: <56C35FE3.5010304@oracle.com> (raw)

Hi all,

I'd like to participate in this year's LSF/MM to continue my
work on improving the testing and validation of MM code.

While I'm currently doing work aimed at improving hugepage related
testing, it's important to understand how other parts of MM can
be easier to test and fuzz.

It'll be interesting to expose other, more untested and/or bitrotten
bits to userspace testing and fuzzing, but it's not clear which parts
are of interest, and which assumptions the existing code makes about
those bits - something we need to clarify.


Thanks,
Sasha

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

                 reply	other threads:[~2016-02-16 17:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=56C35FE3.5010304@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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.