net-test: packetdrill: fix compilation/runtime error for linux 3.x

[particle128]

Hi,

I found this little issue when using packetdrill under linux 3.10. Would you kindly help review the following pull request?

For linux 3.10, TCP_CC_INFO and SO_MEMINFO are not supported. When we define HAVE_SO_MEMINFO / HAVE_TCP_CC_INFO as 0, functions like write_tcp_bbr_cc_info and write_so_meminfo will not be accessed. So wrap them with #ifdef and #endif.

Also, for lower linux version, tcp_info option value has less fields(e.g. 120 bytes). So remove the size assert.

Thanks,
Particle128

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[particle128]

I signed it!

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.

[googlebot]

CLAs look good, thanks!

[particle128]

Could you kindly help review the PR ?

Thanks,
Particle128

[HughLu]

do ./configure and make in packetdrill project , have error info : make: Makefile: No such file or directory
make: *** No rule to make target `Makefile'. Stop.
I build it in imac computer
Can you tell what can I do? Thanks

[nealcardwell]

Hi. Thank you for your contribution! Sorry for the delay in reviewing this.

I have proposed a version of this pull request with a slightly tweaked formatting of the commit description:
#35

Can you please either:

(A) update your pull request #13 to match the formatting of #35 with an added Signed-off-by: footer containing your name and preferred email.

or

(B) post a message in #35 to confirm that you are OK with the edits I made by leaving a comment that contains only "@googlebot I consent." in the pull request #35

Thanks!
neal