From: Thomas Gleixner <tglx@linutronix•de>
To: Heiner Kallweit <hkallweit1@gmail•com>,
kernel test robot <oliver.sang@intel•com>
Cc: Michael Kelley <mikelley@microsoft•com>,
Nishanth Menon <nm@ti•com>, Jason Gunthorpe <jgg@nvidia•com>,
LKML <linux-kernel@vger•kernel.org>,
x86@kernel•org, lkp@lists•01.org, lkp@intel•com,
nic_swsd@realtek•com, "David S. Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
netdev@vger•kernel.org
Subject: Re: [genirq/msi] 495c66aca3: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c
Date: Mon, 10 Jan 2022 21:43:36 +0100 [thread overview]
Message-ID: <87fspvqq2v.ffs@tglx> (raw)
In-Reply-To: <da2cd97c-bd64-ebbd-549b-259ca56e3023@gmail.com>
On Tue, Dec 28 2021 at 20:25, Heiner Kallweit wrote:
> On 28.12.2021 19:40, Thomas Gleixner wrote:
>> if (jumbo_max)
>> netdev_info(dev, "jumbo features [frames: %d bytes, tx checksumming: %s]\n",
>
> Thanks for the patch, I'll submit it with your SoB.
Thank you!
> Apart from pci_irq_vector() incl. underlying msi_get_virq(), are there
> more functions that must not be called from atomic context any longer?
I don't think so. The allocation/free functions were always restricted
to preemptible context.
> Maybe the new constraint should be added to kernel-doc of affected
> functions?
Probably.
Thanks,
tglx
prev parent reply other threads:[~2022-01-10 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211227150535.GA16252@xsang-OptiPlex-9020>
2021-12-28 18:40 ` [genirq/msi] 495c66aca3: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c Thomas Gleixner
2021-12-28 19:25 ` Heiner Kallweit
2022-01-10 20:43 ` Thomas Gleixner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fspvqq2v.ffs@tglx \
--to=tglx@linutronix$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=hkallweit1@gmail$(echo .)com \
--cc=jgg@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lkp@intel$(echo .)com \
--cc=lkp@lists$(echo .)01.org \
--cc=mikelley@microsoft$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nic_swsd@realtek$(echo .)com \
--cc=nm@ti$(echo .)com \
--cc=oliver.sang@intel$(echo .)com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox