netdev - Re: [PATCH v2 net] qed/qede: Fix scheduling while atomic

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: <20230425084104.1a92b0dd@kernel.org>
Date:   Tue, 25 Apr 2023 08:41:04 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Manish Chopra <manishc@...vell.com>
Cc:     <netdev@...r.kernel.org>, <aelior@...vell.com>,
        <palok@...vell.com>, Sudarsana Kalluru <skalluru@...vell.com>,
        "David S . Miller" <davem@...emloft.net>
Subject: Re: [PATCH v2 net] qed/qede: Fix scheduling while atomic

On Tue, 25 Apr 2023 06:50:35 -0700 Manish Chopra wrote:
> Bonding module collects the statistics while holding
> the spinlock, beneath that qede->qed driver statistics
> flow gets scheduled out due to usleep_range() used in PTT
> acquire logic which results into below bug and traces -

Quoting documentation:

  Resending after review
  ~~~~~~~~~~~~~~~~~~~~~~

  Allow at least 24 hours to pass between postings. This will ensure reviewers
  from all geographical locations have a chance to chime in. Do not wait
  too long (weeks) between postings either as it will make it harder for reviewers
  to recall all the context.

  Make sure you address all the feedback in your new posting. Do not post a new
  version of the code if the discussion about the previous version is still
  ongoing, unless directly instructed by a reviewer.

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#resending-after-review