Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 19 Aug 2019 09:06:19 +0300
From:   Emil Karlson <jekarl@iki.fi>
To:     Stanislaw Gruszka <sgruszka@redhat.com>
Cc:     Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: Ap mode regression in linux-5.3-rc1 in rt2800usb
Message-ID: <20190819090619.54f523cb@lettuce>
In-Reply-To: <20190816093302.GA2158@redhat.com>
References: <20190813215000.6cc27ade@lettuce>
        <20190814085018.GA29199@redhat.com>
        <20190816110012.63982001@lettuce>
        <20190816093302.GA2158@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Hi

On Fri, 16 Aug 2019 11:33:02 +0200
Stanislaw Gruszka <sgruszka@redhat.com> wrote:

> > > > After upgrading my ap running rt2800usb to linux-5.3-rc1 I
> > > > noticed an unusual problem of not being able to connect to my
> > > > ap with my android devices (nexus7/flo and nexus5x/bullhead),
> > > > from tcpdump it seemed ap was receiving packets from the
> > > > android devices after successful association, but android
> > > > devices were not seeing the dhcp replies.
> > > > 
> > > > I reverted drivers/net/wireless/ralink to the state it is in
> > > > v5.2.8 and android clients can connect again normally. I did not
> > > > explicitly set watchdog parameter to any value.
> > 
> > > Most suspicious are 710e6cc1595e and 41a531ffa4c5 .
> > 
> > It seems to me that reverting only
> > 710e6cc1595e25378c4b9977f7a8b4ad4a72a109
> > allows all my android devices to successfully connect to the
> > internet.
> 
> Please test attached patch as proposed fix for
> 710e6cc1595e25378c4b9977f7a8b4ad4a72a109 and report back. Thanks.

After some testing it seems attached patch fixes the regression with no
observed negative side effects. Thanks.

Best Regards
-Emil