linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Neal Cardwell' <ncardwell@google.com>,
	louisrossberg <louisrossberg@protonmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>
Subject: RE: Listening on a TCP socket from a Kernel Module
Date: Mon, 17 May 2021 12:50:30 +0000	[thread overview]
Message-ID: <576922badb254ef0a73443a7752ba9c8@AcuMS.aculab.com> (raw)
In-Reply-To: <CADVnQymGvCTEzdd8dSLZnn0dwnHAoNiwo72yEFeNr47+Na8GDg@mail.gmail.com>

From: Neal Cardwell
> Sent: 17 May 2021 02:55
> 
> On Sun, May 16, 2021 at 7:20 PM louisrossberg
> <louisrossberg@protonmail.com> wrote:
> >
> > Hello, can somebody point me in the right direction for
> > what I would use to listen on a TCP socket from the
> > kernel? I am working on a kernel module and have spent the
> > past day looking through include/net and include/linux for
> > something that would allow me to do so. I know TCP
> > listening is typically done in userspace, but it should be
> > possible at the kernel level right?  tcp_diag looks
> > promising, but it seems like that is mainly for monitoring
> > sockets, and I'm not sure if I would be able to provide
> > responses from it.
> >
> > Louis Rossberg,
> > Warped Technologies
> 
> Perhaps kernel_listen() and related functions (kernel_bind(),
> kernel_accept(), etc.) in net/socket.c might do the trick for your use
> case? Looking at how the callers of these functions structure their
> code might give you enough to go on.

They should work.
There are a couple of issues though:
- There is no getsockopt() support in current kernels.
- You may need to use __sock_create() rather than sock_create_kern()
  in order to hold a reference to the network namespace.
It may be possible to use the wakeup callbacks that select/poll use.
But it is probably safer to use blocking operations from a separate
kernel thread.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

      reply	other threads:[~2021-05-17 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 23:20 Listening on a TCP socket from a Kernel Module louisrossberg
2021-05-17  1:55 ` Neal Cardwell
2021-05-17 12:50   ` David Laight [this message]

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=576922badb254ef0a73443a7752ba9c8@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=louisrossberg@protonmail.com \
    --cc=ncardwell@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).