Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220613181233.078148768@linuxfoundation.org> <CAK8fFZ68+xZ2Z0vDWnihF8PeJKEmEwCyyF-8W9PCZJTd8zfp-A@mail.gmail.com>
 <YqgsDXdY3OttH8Mc@kroah.com> <CAK8fFZ5SP4zAra2X8B3Q9zkhQGMfif+y-oEvkpR4fDpL8_upKg@mail.gmail.com>
 <YqihnavPcyzMMw8l@kroah.com>
In-Reply-To: <YqihnavPcyzMMw8l@kroah.com>
From:   Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>
Date:   Tue, 14 Jun 2022 17:03:23 +0200
Message-ID: <CAK8fFZ4JnhA3s8e4YDp_+GOq5+p4YzRtKdEFzjogtXc3EBttzw@mail.gmail.com>
Subject: Re: [PATCH 5.18 000/343] 5.18.4-rc2 review
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        torvalds@linux-foundation.org, akpm@linux-foundation.org,
        linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
        lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com,
        f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
        slade@sladewatkins.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

=C3=BAt 14. 6. 2022 v 16:56 odes=C3=ADlatel Greg Kroah-Hartman
<gregkh@linuxfoundation.org> napsal:
>
> On Tue, Jun 14, 2022 at 04:41:31PM +0200, Jaroslav Pulchart wrote:
> > =C3=BAt 14. 6. 2022 v 8:34 odes=C3=ADlatel Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> napsal:
> > >
> > > On Tue, Jun 14, 2022 at 07:56:36AM +0200, Jaroslav Pulchart wrote:
> > > > Hello,
> > > >
> > > > I would like to report that the ethernet ice driver is not capable =
of
> > > > setting promisc mode on at E810-XXV physical interface in the whole
> > > > 5.18.y kernel line.
> > > >
> > > > Reproducer:
> > > >    $ ip link set promisc on dev em1
> > > > Dmesg error message:
> > > >    Error setting promisc mode on VSI 6 (rc=3D-17)
> > > >
> > > > the problem was not observed with 5.17.y
> > >
> > > Any chance you can use 'git bisect' to track down the problem commit =
and
> > > let the developers of it know?
> > >
> > > thanks,
> >
> > I tried it, but it makes the system unbootable. I expect the reason is
> > that it happened somewhere between 5.17->5.18 so I'm using an
> > "unstable" kernel.
> >
> > Is there some way I could bisect just one driver, not a full kernel
> > between 5.17->5.18?
>
> How do you know it is just "one driver"?

Just a quess based on "git grep". The error message was introduced in
the driver in 5.18-rc*.

The idea is to try it per partes. The bisect of the whole kernel makes
stuff unbootable anyway.

>
> Anyway, yes, I think there are options to give to git bisect, you can
> feed it just the path to the driver as part of 'git bisect start' and I
> think that should work.  The man page for 'git bisect' shows this with
> the following example:
>          git bisect start -- arch/i386 include/asm-i386
> to just test changes for those directories.

Thanks for this hint! I'm going to try it.

>
> thanks,
>
> greg k-h

Jaroslav P.