Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20201208172912.4352-1-hadess@hadess.net> <CABBYNZJNTDek+kKS5wtrr67Xx8DmFGvcV13cLSxULgJRa5N+3g@mail.gmail.com>
 <6e6d72ff9aa14a65d6d0df5bd68a6ad6887f31c2.camel@hadess.net> <ebbb9f334f6f0cecdb46ddce63483df165ea12ec.camel@hadess.net>
In-Reply-To: <ebbb9f334f6f0cecdb46ddce63483df165ea12ec.camel@hadess.net>
From:   Archie Pusaka <apusaka@google.com>
Date:   Wed, 6 Jan 2021 17:47:09 +0800
Message-ID: <CAJQfnxEpagJOSVdA0MaHg0foy53K6QSpSYk++OQ18hQue9jYCA@mail.gmail.com>
Subject: Re: [PATCH] Bluetooth: L2CAP: Try harder to accept device not knowing options
To:     Bastien Nocera <hadess@hadess.net>
Cc:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
        "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>,
        Florian Dollinger <dollinger.florian@gmx.de>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Bastien,

For the test L2CAP/COS/CFD/BV-14-C, this patch is required to pass it.
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=5b8ec15d02f12148ef0185825217162b3bc341f4

I don't think it is merged yet into 5.10, so you might need to apply
the patch yourself.

Thanks,
Archie

On Wed, 6 Jan 2021 at 17:28, Bastien Nocera <hadess@hadess.net> wrote:
>
> On Wed, 2020-12-16 at 16:49 +0100, Bastien Nocera wrote:
> > <snip>
> > The tests fail for me in the same on a kernel with and without
> > the
> > patch:
> > - Expected that the IUT transmits an L2CAP_ConfigRsp includes the
> > unsupported option that Lower Tester sent.
> > Final Verdict:FAIL
> > L2CAP/COS/CFD/BV-14-C finished
> >
> > Is this expected? I was using an 5.10-rc7 kernel with and without the
> > patch I sent. I can send you the full results off-list if you want
> > them.
>
> Any news on that? Is the error expected, should I test with a newer
> version of the kernel? I'd really like to finally land this...
>