diff options
| author | Lorenzo Colitti <lorenzo@google.com> | 2019-03-21 22:10:26 +0900 |
|---|---|---|
| committer | Lorenzo Colitti <lorenzo@google.com> | 2019-03-22 21:05:14 +0900 |
| commit | 4c16d95aa2a804b8289a34e517f95ce35c4a8adc (patch) | |
| tree | 2e3995a334998dcdf25ec919d2f527457d286b1f /annotations/generate_annotated_java_files.py | |
| parent | 7fdf2272c4f9519e2e155e7c198e6482558f97c0 (diff) | |
Don't crash when passing null destinations to bind, connect, and sendto
Passing a null address to bind or connect is invalid (for
AF_INET6 socekts, they return EINVAL), so throw NPE. Passing a
null address to sendto is valid and means "send to the address
this socket is connected to". Pass the call to the kernel as
the app would expect.
There should be no backwards compatibility implications to this
change because previously these operations would just crash with
a JNI error. See previous CL in topic.
Bug: 126699941
Test: atest CtsLibcoreTestCases:libcore.libcore.io.OsTest#testCrossFamilyBindConnectSendto
Change-Id: I1d36c13e8d0ee426993f4bab33cfcfdc1603bfc8
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions