netdev - RE: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <MW4PR11MB57766A32DF641A69831B610EFD309@MW4PR11MB5776.namprd11.prod.outlook.com>
Date:   Fri, 11 Feb 2022 10:05:54 +0000
From:   "Drewek, Wojciech" <wojciech.drewek@...el.com>
To:     Harald Welte <laforge@...ocom.org>,
        Marcin Szycik <marcin.szycik@...ux.intel.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "michal.swiatkowski@...ux.intel.com" 
        <michal.swiatkowski@...ux.intel.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "pablo@...filter.org" <pablo@...filter.org>,
        "osmocom-net-gprs@...ts.osmocom.org" 
        <osmocom-net-gprs@...ts.osmocom.org>
Subject: RE: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device
 without FDs



> -----Original Message-----
> From: Harald Welte <laforge@...ocom.org>
> Sent: piątek, 11 lutego 2022 10:12
> To: Marcin Szycik <marcin.szycik@...ux.intel.com>
> Cc: netdev@...r.kernel.org; michal.swiatkowski@...ux.intel.com; Drewek, Wojciech <wojciech.drewek@...el.com>;
> davem@...emloft.net; kuba@...nel.org; pablo@...filter.org; osmocom-net-gprs@...ts.osmocom.org
> Subject: Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
> 
Hi Harald,

Thanks for triggering CI.
Do I see correctly that results for our changes are the same as for master?

Regards,
Wojtek
> Hi Marcin,
> 
> On Wed, Feb 09, 2022 at 07:04:01PM +0100, Marcin Szycik wrote:
> > On 05-Feb-22 17:34, Harald Welte wrote:
> > > Hi Marcin, Wojciech,
> > >
> > > thanks for the revised patch. In general it looks fine to me.
> > >
> > > Do you have a public git tree with your patchset applied?  I'm asking as
> > > we do have automatic testing in place at https://jenkins.osmocom.org/ where I
> > > just need to specify a remote git repo andit will build this kernel and
> > > run the test suite.
> >
> > I've created a public fork with our patchset applied, please see [1].
> 
> Thanks, I've triggered a build, let's hope it works out.  Results should
> be at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/
> and detailed logs at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/console
> 
> The same testsuite executed  against master can be seen at
> https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-latest-torvalds/
> [the high amount of test cases failing is due to the lack of IPv6 support in the kernel GTP].
> 
> Let's hope your forked repo renders identical test results to upstream!
> 
> Regards,
> 	Harald
> --
> - Harald Welte <laforge@...ocom.org>            http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                   (ETSI EN 300 175-7 Ch. A6)