From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: bugs@lists.linux.dev, netdev@vger.kernel.org,
john.fastabend@gmail.com, kuba@kernel.org, borisp@nvidia.com
Subject: Re: TCP_ULP option is not working for tls
Date: Thu, 4 May 2023 16:19:29 +0000 (UTC) [thread overview]
Message-ID: <20230504-b217401c2-ed16c78b19c6@bugzilla.kernel.org> (raw)
In-Reply-To: <20230504-b217401c0-873168e318a9@bugzilla.kernel.org>
sumit.200744 writes via Kernel.org Bugzilla:
I tried it on 5.15.78 where I'm getting the above failure - "No such file or directory for setsockopt.
Not sure on which linux kernel this TLS option is introduced.
View: https://bugzilla.kernel.org/show_bug.cgi?id=217401#c2
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next prev parent reply other threads:[~2023-05-04 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 16:19 TCP_ULP option is not working for tls Kernel.org Bugbot
2023-05-04 16:19 ` Kernel.org Bugbot [this message]
2023-05-04 16:51 ` Jakub Kicinski
2023-05-04 16:19 ` Kernel.org Bugbot
2023-05-05 7:09 ` Kernel.org Bugbot
2023-05-05 19:43 ` Kernel.org Bugbot
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=20230504-b217401c2-ed16c78b19c6@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=borisp@nvidia.com \
--cc=bugs@lists.linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.