From: kernel test robot <lkp@intel.com>
To: David Arinzon <darinzon@amazon.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Paolo Abeni <pabeni@redhat.com>,
Shay Agroskin <shayagr@amazon.com>
Subject: drivers/net/ethernet/amazon/ena/ena_netdev.c:77 ena_tx_timeout() warn: inconsistent indenting
Date: Sun, 1 Dec 2024 21:42:17 +0800 [thread overview]
Message-ID: <202412012100.tEFoTQaX-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: bcc8eda6d34934d80b96adb8dc4ff5dfc632a53a
commit: 071271f39ce833a3534d1fbd47174d1bed6d9326 net: ena: Add more information on TX timeouts
date: 10 months ago
config: x86_64-randconfig-161-20241122 (https://download.01.org/0day-ci/archive/20241201/202412012100.tEFoTQaX-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412012100.tEFoTQaX-lkp@intel.com/
smatch warnings:
drivers/net/ethernet/amazon/ena/ena_netdev.c:77 ena_tx_timeout() warn: inconsistent indenting
vim +77 drivers/net/ethernet/amazon/ena/ena_netdev.c
47
48 static void ena_tx_timeout(struct net_device *dev, unsigned int txqueue)
49 {
50 enum ena_regs_reset_reason_types reset_reason = ENA_REGS_RESET_OS_NETDEV_WD;
51 struct ena_adapter *adapter = netdev_priv(dev);
52 unsigned int time_since_last_napi, threshold;
53 struct ena_ring *tx_ring;
54 int napi_scheduled;
55
56 if (txqueue >= adapter->num_io_queues) {
57 netdev_err(dev, "TX timeout on invalid queue %u\n", txqueue);
58 goto schedule_reset;
59 }
60
61 threshold = jiffies_to_usecs(dev->watchdog_timeo);
62 tx_ring = &adapter->tx_ring[txqueue];
63
64 time_since_last_napi = jiffies_to_usecs(jiffies - tx_ring->tx_stats.last_napi_jiffies);
65 napi_scheduled = !!(tx_ring->napi->state & NAPIF_STATE_SCHED);
66
67 netdev_err(dev,
68 "TX q %d is paused for too long (threshold %u). Time since last napi %u usec. napi scheduled: %d\n",
69 txqueue,
70 threshold,
71 time_since_last_napi,
72 napi_scheduled);
73
74 if (threshold < time_since_last_napi && napi_scheduled) {
75 netdev_err(dev,
76 "napi handler hasn't been called for a long time but is scheduled\n");
> 77 reset_reason = ENA_REGS_RESET_SUSPECTED_POLL_STARVATION;
78 }
79 schedule_reset:
80 /* Change the state of the device to trigger reset
81 * Check that we are not in the middle or a trigger already
82 */
83 if (test_and_set_bit(ENA_FLAG_TRIGGER_RESET, &adapter->flags))
84 return;
85
86 ena_reset_device(adapter, reset_reason);
87 ena_increase_stat(&adapter->dev_stats.tx_timeout, 1, &adapter->syncp);
88 }
89
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-12-01 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 13:42 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 15:55 drivers/net/ethernet/amazon/ena/ena_netdev.c:77 ena_tx_timeout() warn: inconsistent indenting kernel test robot
2024-12-10 9:14 kernel test robot
2024-11-29 6:17 kernel test robot
2024-11-04 14:34 kernel test robot
2024-09-15 9:59 kernel test robot
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=202412012100.tEFoTQaX-lkp@intel.com \
--to=lkp@intel.com \
--cc=darinzon@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=shayagr@amazon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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