netdev - Re: [PATCH net-next v2 1/1] ibmvnic: add some debugs

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 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]

Date:   Wed, 2 Dec 2020 19:33:19 -0800
From:   Sukadev Bhattiprolu <sukadev@...ux.ibm.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     netdev@...r.kernel.org, Dany Madden <drt@...ux.ibm.com>,
        Lijun Pan <ljp@...ux.ibm.com>
Subject: Re: [PATCH net-next v2 1/1] ibmvnic: add some debugs

Jakub Kicinski [kuba@...nel.org] wrote:
> On Mon, 23 Nov 2020 20:34:07 -0800 Sukadev Bhattiprolu wrote:
> > We sometimes run into situations where a soft/hard reset of the adapter
> > takes a long time or fails to complete. Having additional messages that
> > include important adapter state info will hopefully help understand what
> > is happening, reduce the guess work and minimize requests to reproduce
> > problems with debug patches.
> > 
> > Signed-off-by: Sukadev Bhattiprolu <sukadev@...ux.ibm.com>
> > ---
> > 
> > Changelog[v2]
> > 	[Jakub Kacinski] Change an netdev_err() to netdev_info()? Changed
> > 	to netdev_dbg() instead. Also sending to net rather than net-next.
> > 
> > 	Note: this debug patch is based on following bug fixes and a feature
> > 	from Dany Madden and Lijun Pan:
> 
> In which case you need to wait for these prerequisites to be in net-next
> and then repost.

Jakub,

A process question that I could not find an answer to on the netdev FAQ.

With commit 98c41f04a67a ("ibmvnic: reduce wait for completion time")
the pre-requisites for the above patch are in the net tree but not yet
in net-next.

When net-next is open, does it get periodically rebased to net tree or
does the rebase happen only when net-next closes?

If latter, should I resend above patch based on net-next and handle a
manual merge during the rebase? (There is no functional dependence on
the pre-reqs - just needs a manual merge).

Thanks,

Sukadev