From: Mykola Lysenko <mykolal@fb.com>
To: Qiao Ma <mqaio@linux.alibaba.com>
Cc: Mykola Lysenko <mykolal@fb.com>,
"andrii@kernel.org" <andrii@kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH bpf-next] selftests/bpf: fix incorrect fcntl call
Date: Wed, 24 Aug 2022 15:03:23 +0000 [thread overview]
Message-ID: <9BE5800D-DA65-485A-8E5E-5B84F59F70BD@fb.com> (raw)
In-Reply-To: <a46dffe36f2570ec91761b1d604ac52fa0a10efb.1661348961.git.mqaio@linux.alibaba.com>
Hi Qiao,
> On Aug 24, 2022, at 7:01 AM, Qiao Ma <mqaio@linux.alibaba.com> wrote:
>
> !-------------------------------------------------------------------|
> This Message Is From an External Sender
>
> |-------------------------------------------------------------------!
>
> To set socket noblock, we need to use
>> fcntl(fd, F_SETFL, O_NONBLOCK);
> rather than:
>> fcntl(fd, O_NONBLOCK);
Can you please add more description on what is it fixing?
Additionally, add file name to the title to make it easier to identify the commit from oneline git log.
Something like “selftests/bpf: fix incorrect fcntl call (test_sockmap.c)”.
Thank you!
>
> Signed-off-by: Qiao Ma <mqaio@linux.alibaba.com>
> ---
> tools/testing/selftests/bpf/test_sockmap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/bpf/test_sockmap.c b/tools/testing/selftests/bpf/test_sockmap.c
> index 0fbaccdc8861..b163b7cfd957 100644
> --- a/tools/testing/selftests/bpf/test_sockmap.c
> +++ b/tools/testing/selftests/bpf/test_sockmap.c
> @@ -598,7 +598,7 @@ static int msg_loop(int fd, int iov_count, int iov_length, int cnt,
> struct timeval timeout;
> fd_set w;
>
> - fcntl(fd, fd_flags);
> + fcntl(fd, F_SETFL, fd_flags);
> /* Account for pop bytes noting each iteration of apply will
> * call msg_pop_data helper so we need to account for this
> * by calculating the number of apply iterations. Note user
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2022-08-24 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 14:01 Qiao Ma
2022-08-24 15:03 ` Mykola Lysenko [this message]
2022-08-24 15:50 ` Alexei Starovoitov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9BE5800D-DA65-485A-8E5E-5B84F59F70BD@fb.com \
--to=mykolal@fb.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mqaio@linux.alibaba.com \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®