diff options
| author | Dean Deng <deandeng@google.com> | 2021-01-20 16:56:58 -0800 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2021-01-20 17:01:00 -0800 |
| commit | a733a8142e42b5405cb9b0da41b051dfd2f03716 (patch) | |
| tree | 5ac8fe813d107e707c9d22c900ca2f4ac1afce10 /test | |
| parent | 55332aca95a55378957f89a10f21d9d1714070a5 (diff) | |
Fix typo boundry -> boundary.
PiperOrigin-RevId: 352905565
Diffstat (limited to 'test')
| -rw-r--r-- | test/syscalls/linux/socket_unix_cmsg.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/syscalls/linux/socket_unix_cmsg.cc b/test/syscalls/linux/socket_unix_cmsg.cc index a16899493..22a4ee0d1 100644 --- a/test/syscalls/linux/socket_unix_cmsg.cc +++ b/test/syscalls/linux/socket_unix_cmsg.cc @@ -362,7 +362,7 @@ TEST_P(UnixSocketPairCmsgTest, BasicThreeFDPassTruncationMsgCtrunc) { // BasicFDPassUnalignedRecv starts off by sending a single FD just like // BasicFDPass. The difference is that when calling recvmsg, the length of the -// receive data is only aligned on a 4 byte boundry instead of the normal 8. +// receive data is only aligned on a 4 byte boundary instead of the normal 8. TEST_P(UnixSocketPairCmsgTest, BasicFDPassUnalignedRecv) { auto sockets = ASSERT_NO_ERRNO_AND_VALUE(NewSocketPair()); |