Page MenuHomeFreeBSD

Inconsistencies in DOF sections headers and sections
ClosedPublic

Authored by graeme.jenkinson_cl.cam.ac.uk on Oct 2 2019, 1:22 PM.

Details

Summary

The DOF file output by dtrace -A contains only the loadable sections. However, as it was created by a call to dtrace_dof_create without flags, the original DOF was created with the loadable sections. The result is that the DOF includes the section headers for the unloadable sections (COMMENTS and UTSNAME) without these sections actually being present. This is inconsistent.

A simple change to anon_prog() in dtrace.c (cddl/contrib/opensolaris/cmd/dtrace) ensures that the missing sections are present in the outputted DOF. Alternatively, the call to dtrace_dof_create() could pass the DTRACE_D_STRIP flag stripping out the loadable sections. As the unloadable sections contain info useful for debugging purposes they haven't been stripped.

Test Plan

Tested change by created DOF - dtrace -A - and confirming that the missing sections are included in the resulting DOF and that the contain the correct information. Also confirmed that the other DOF sections remain valid.

Diff Detail

Lint
Lint Skipped
Unit
Unit Tests Skipped

Event Timeline

This makes sense to me, thanks. I'll commit it in a day or two if no one else jumps in.

This makes sense to me, thanks. I'll commit it in a day or two if no one else jumps in.

Cool. It's only a minor thing but we are increasingly relying on correct knowledge of the internals of DIF and DOF to do our work on distribution.

This makes sense to me, thanks. I'll commit it in a day or two if no one else jumps in.

Cool. It's only a minor thing but we are increasingly relying on correct knowledge of the internals of DIF and DOF to do our work on distribution.

Is there a "Sponsored by:" tag you'd like added to the commit message?

This makes sense to me, thanks. I'll commit it in a day or two if no one else jumps in.

Cool. It's only a minor thing but we are increasingly relying on correct knowledge of the internals of DIF and DOF to do our work on distribution.

Is there a "Sponsored by:" tag you'd like added to the commit message?

I'll just double check with Robert, I've just got a letter about contract extension. I think this is funded differently. Robert says DARPA/AFRL ATM, so some/all of the following blurb?

This software was developed by BAE Systems, the University of Cambridge Computer Laboratory, and Memorial University under DARPA/AFRL contract FA8650-15-C-7558 ("CADETS"), as part of the DARPA Transparent Computing (TC) research program.

Let me know if I should be putting this somewhere I couldn't see a way I can add this.

This makes sense to me, thanks. I'll commit it in a day or two if no one else jumps in.

Cool. It's only a minor thing but we are increasingly relying on correct knowledge of the internals of DIF and DOF to do our work on distribution.

Is there a "Sponsored by:" tag you'd like added to the commit message?

I'll just double check with Robert, I've just got a letter about contract extension. I think this is funded differently. Robert says DARPA/AFRL ATM, so some/all of the following blurb?

This software was developed by BAE Systems, the University of Cambridge Computer Laboratory, and Memorial University under DARPA/AFRL contract FA8650-15-C-7558 ("CADETS"), as part of the DARPA Transparent Computing (TC) research program.

Let me know if I should be putting this somewhere I couldn't see a way I can add this.

Sorry, I don't get a notification when you edit an existing message.

I believe we typically use "Sponsored by: DARPA/AFRL" in that case. There are many examples of this in the tree. I'll go ahead and commit with that tomorrow if you have no objection.

This revision was not accepted when it landed; it landed in state Needs Review.Nov 18 2019, 6:34 PM
This revision was automatically updated to reflect the committed changes.