From: Tom Parkin <tparkin@katalix.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
James Chapman <jchapman@katalix.com>,
edumazet@google.com, gnault@redhat.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv4] PPPoL2TP: Add more code snippets
Date: Tue, 13 Feb 2024 12:58:40 +0000 [thread overview]
Message-ID: <ZctngNzLYe/+Iman@katalix.com> (raw)
In-Reply-To: <20240213115304.3oyqkvkb3oqkauwd@begin>
[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]
On Tue, Feb 13, 2024 at 12:53:04 +0100, Samuel Thibault wrote:
> Tom Parkin, le mar. 13 févr. 2024 10:51:08 +0000, a ecrit:
> > > + ret = ioctl(session_fd1, PPPIOCGCHAN, &chindx1);
> > > + if (ret < 0)
> > > + return -errno;
> > > +
> > > + ret = ioctl(session_fd2, PPPIOCGCHAN, &chindx2);
> > > + if (ret < 0)
> > > + return -errno;
> > > +
> > > + ppp_chan_fd = open("/dev/ppp", O_RDWR);
> > > + if (ppp_chan_fd < 0) {
> > > + return -errno;
> > > + }
> > > +
> > > + ret = ioctl(ppp_chan_fd, PPPIOCATTCHAN, &chindx1);
> > > + if (ret < 0) {
> > > + close(ppp_chan_fd);
> > > + return -errno;
> > > + }
> >
> > I think we should drop the PPPIOCATTCHAN ioctl call here.
> >
> > The input file descriptors are called out as being PPPoX sockets
> > created as described earlier, in which case they should both
> > already be attached to a channel.
> >
> > It would make more sense IMO to call out the two ppp_chan_fd file
> > descriptors as being input parameters alongside the PPPoX session file
> > descriptors.
> >
> > > +
> > > + ret = ioctl(ppp_chan_fd, PPPIOCBRIDGECHAN, &chindx2);
> > > + close(ppp_chan_fd);
> > > + if (ret < 0)
> > > + return -errno;
> > > +
> > > +It can be noted that in this case no PPP interface is needed, and the PPP
> > > +channel does not need to be kept open. Only the session PPPoX data sockets need
> > > +to be kept open.
> >
> > Is it true to say that the PPP channel file descriptors can be closed
> > by userspace?
>
> In our code we do it
> https://code.ffdn.org/sthibaul/l2tpns/-/blob/kernel/l2tpns.c?ref_type=heads#L1295
> and it works all fine indeed (and avoids that fd per session).
>
> That's actually one of the reason why I made the snipped only take the
> pppox sockets, and make it create the ppp chan fd only temporarily. AIUI
> the pppox socket already has a ppp chan (returned by PPPIOCGCHAN), and
> the ppp chan fd is there only for performing the bridging ioctl.
Thanks for the code reference -- that makes it clearer. And I'm glad
someone (else) is using PPPIOCBRIDGECHAN :-)
It's a while since I was looking in ppp_generic.c and you're right
about the ppp channel fd.
--
Tom Parkin
Katalix Systems Ltd
https://katalix.com
Catalysts for your Embedded Linux software development
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-02-13 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 22:23 Samuel Thibault
2024-02-13 10:51 ` Tom Parkin
2024-02-13 11:53 ` Samuel Thibault
2024-02-13 12:58 ` Tom Parkin [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=ZctngNzLYe/+Iman@katalix.com \
--to=tparkin@katalix.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=samuel.thibault@ens-lyon.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®