All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Fiona Ebner <f.ebner@proxmox.com>, linux-kernel@vger.kernel.org
Cc: siva.kallam@broadcom.com, prashant@broadcom.com,
	mchan@broadcom.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
	jdelvare@suse.com, Guenter Roeck <linux@roeck-us.net>,
	netdev@vger.kernel.org, linux-hwmon@vger.kernel.org,
	keescook@chromium.org,
	Linux Regressions <regressions@lists.linux.dev>
Subject: Re: "Use slab_build_skb() instead" deprecation warning triggered by tg3
Date: Fri, 18 Aug 2023 18:12:33 +0700	[thread overview]
Message-ID: <ZN9SId_KNgI3dfVI@debian.me> (raw)
In-Reply-To: <1bd4cb9c-4eb8-3bdb-3e05-8689817242d1@proxmox.com>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

On Fri, Aug 18, 2023 at 10:05:11AM +0200, Fiona Ebner wrote:
> Hi,
> we've got a user report about the WARN_ONCE introduced by ce098da1497c
> ("skbuff: Introduce slab_build_skb()") [0]. The stack trace indicates
> that the call comes from the tg3 module. While this is still kernel 6.2
> and I can't verify that the issue is still there with newer kernels, I
> don't see related changes in drivers/net/ethernet/broadcom/tg3.* after
> ce098da1497c, so I thought I should let you know.
> 

Thanks for the regression report. I'm adding it to regzbot:

#regzbot ^introduced: ce098da1497c6d
#regzbot link: https://forum.proxmox.com/threads/132338/

PS: The proxmox forum link (except full dmesg log pasted there) is in
German, so someone fluent in the language can be helpful here.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-08-18 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  8:05 "Use slab_build_skb() instead" deprecation warning triggered by tg3 Fiona Ebner
2023-08-18 11:12 ` Bagas Sanjaya [this message]
2023-08-18 11:22   ` Fiona Ebner
2023-08-18 17:37   ` Kees Cook

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=ZN9SId_KNgI3dfVI@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.ebner@proxmox.com \
    --cc=jdelvare@suse.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=prashant@broadcom.com \
    --cc=regressions@lists.linux.dev \
    --cc=richardcochran@gmail.com \
    --cc=siva.kallam@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.