Svadev mailing list

["Adve, Vikram Sadanand" <vadve AT illinois.edu>]

Please send such messages to 
svadev AT cs.uiuc.edu<mailto:svadev AT cs.uiuc.edu>.
  I am sending this there.

--Vikram
Associate Professor, Computer Science
University of Illinois at Urbana-Champaign
http://llvm.org/~vadve



Begin forwarded message:

From: 
"sva-owner AT cs.uiuc.edu<mailto:sva-owner AT cs.uiuc.edu>"
 
<sva-owner AT cs.uiuc.edu<mailto:sva-owner AT cs.uiuc.edu>>
Date: October 7, 2010 10:49:09 PM CDT
To: 
"sva-owner AT cs.uiuc.edu<mailto:sva-owner AT cs.uiuc.edu>"
 
<sva-owner AT cs.uiuc.edu<mailto:sva-owner AT cs.uiuc.edu>>
Subject: sva post from 
tchammah AT uwaterloo.ca<mailto:tchammah AT uwaterloo.ca>
 requires approval

As list administrator, your authorization is requested for the
following mailing list posting:

   List:    
sva AT cs.uiuc.edu<mailto:sva AT cs.uiuc.edu>
   From:    
tchammah AT uwaterloo.ca<mailto:tchammah AT uwaterloo.ca>
   Subject: Re: steens-aa (Will are you there?)
   Reason:  Post by non-member to a members-only list

At your convenience, visit:

   http://lists.cs.uiuc.edu/mailman/admindb/sva

to approve or deny the request.

From: Tarek Chammah 
<tchammah AT uwaterloo.ca<mailto:tchammah AT uwaterloo.ca>>
Date: October 7, 2010 10:48:59 PM CDT
To: 
"willdtz AT gmail.com<mailto:willdtz AT gmail.com>"
 
<willdtz AT gmail.com<mailto:willdtz AT gmail.com>>,
 Secure Virtual Architecture List 
<sva AT cs.uiuc.edu<mailto:sva AT cs.uiuc.edu>>
Subject: Re: steens-aa (Will are you there?)


Hello, is anyone out there?

Tarek


On Thu, Oct 7, 2010 at 1:34 AM, Tarek Chammah 
<tchammah AT uwaterloo.ca<mailto:tchammah AT uwaterloo.ca>>
 wrote:
Will, did you receive my earlier reply?

Tarek


On Mon, Oct 4, 2010 at 12:54 AM, Tarek Chammah 
<tchammah AT uwaterloo.ca<mailto:tchammah AT uwaterloo.ca>>
 wrote:
Hey thanks Will, yeah no problem, given the nature of email these
things can happen.

Thanks for forwarding my query on the poolalloc status to the list;
they should know more.

So yeah that patch for the revision in question would be good.  I can
then see if it is worthwhile to port over, or if the codebases have
really diverged to the point of no return.

Thanks and regards,

Tarek


On Sun, Oct 3, 2010 at 11:46 PM, Will Dietz 
<willdtz AT gmail.com<mailto:willdtz AT gmail.com>>
 wrote:
Hi Tarek!

I'm very sorry, I apparently have been replying..somehow.. to the
wrong 'Tarek'.  Some bug in my mail client, sigh, probably combined
with user error.

I can definitely get you any patch you'd like, but am slightly
reluctant to give an impression I'm clear on the status of 2.6
poolalloc overall, as I am not.  I have been working on poolalloc
starting somewhere before 2.7, and as such can't really speak for how
it works on 2.6.

As such, I'm forwarding this message to the SVA mailing list which has
many of the people who know more about poolalloc, particularly its
historical progress... and are probably the people best equipped to
answer this question and others you might have.

Of course, I'll do what I can to help as well :).  To that end, what
are you interested in?  The commit diff for that particular revision?

Anyway, I'd like to apologize again for letting this go so long unanswered.

Here's hoping we can get poolalloc working for you and your project soon :).

~Will

On Sun, Oct 3, 2010 at 12:02 PM, Tarek Chammah 
<tchammah AT uwaterloo.ca<mailto:tchammah AT uwaterloo.ca>>
 wrote:
Hi Will,

Might you have the diff for r105302 against the prior mainline when
you had committed the fix back then?  I can attempt to port it to 2.6.
 Are there any major bugs in 2.6 DSA other than this?

Sincerely,

Tarek


Hi Dineth,

There's a bug in DSA on 2.6 that marked everything incomplete.  It's
since been fixed, although the current HEAD is a work-in-progress...
I'm not sure how it compares to the stability/results of 2.6 (assuming
using 2.7 is even an option for you).  Not really prepared to make
that kind of assessment presently.

The issue you describe was fixed in r105302, but DSA was restructured
a bit since then so the patch won't apply cleanly to 2.6.

Attached is a hack of a fix, that simply says if the code has a call
to va_start mark all nodes incomplete since the behavior isn't modeled
correctly in 2.6 DSA anyway.  Should work fine as long as you aren't
analyzing code with var-arg function definitions.

Hope this helps,

~Will Dietz




From: 
"sva-request AT cs.uiuc.edu<mailto:sva-request AT cs.uiuc.edu>"
 
<sva-request AT cs.uiuc.edu<mailto:sva-request AT cs.uiuc.edu>>
Subject: confirm a8ad28e2dbc4e6f583cfe5fd1aa374cf48b30c6b


If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.