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: <CAA8Zg7FQL6Ong+70qpbh23ooORJ0C5_mZGCP_Tjw2zYHQBKxAw@mail.gmail.com>
Date:   Tue, 20 Oct 2020 17:55:20 +0530
From:   Reji Thomas <rejithomas.d@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Reji Thomas <rejithomas@...iper.net>, davem@...emloft.net,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel test robot <lkp@...el.com>,
        Mathieu Xhonneux <m.xhonneux@...il.com>,
        David Lebrun <david.lebrun@...ouvain.be>
Subject: Re: [PATCH v2] IPv6: sr: Fix End.X nexthop to use oif.

On Mon, Oct 19, 2020 at 9:47 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> If we can save the device lookup and still be semantically correct,
> that's probably better.
I am afraid we need to do a device lookup if I am looking up the
neighbor. neigh_lookup
apis expect dev to be passed. If I go through the current lookup ie
ip6_pol_route() I can
drop the dev lookup at risk of returning a non neighbor route as it
exists today.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ