From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+38a095a81f30d82884c1@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] general protection fault in put_page (4)
Date: Thu, 19 Dec 2024 07:14:56 +0800 [thread overview]
Message-ID: <20241218231457.288-1-hdanton@sina.com> (raw)
In-Reply-To: <6761aed9.050a0220.29fcd0.006b.GAE@google.com>
On Tue, Dec 17, 2024 at 6:03 PM
> syzbot found the following issue on:
>
> HEAD commit: 78d4f34e2115 Linux 6.13-rc3
> git tree: upstream
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f502df980000
#syz test
--- x/net/core/skbuff.c
+++ y/net/core/skbuff.c
@@ -1099,13 +1099,22 @@ static void skb_free_head(struct sk_buff
}
}
+static DEFINE_SPINLOCK(skb_release_data_lock);
static void skb_release_data(struct sk_buff *skb, enum skb_drop_reason reason)
{
struct skb_shared_info *shinfo = skb_shinfo(skb);
int i;
+ unsigned long flg;
if (!skb_data_unref(skb, shinfo))
- goto exit;
+ return;
+ spin_lock_irqsave(&skb_release_data_lock, flg);
+ if ((1 << 6) & shinfo->flags) {
+ spin_unlock_irqrestore(&skb_release_data_lock, flg);
+ return;
+ }
+ shinfo->flags |= (1 << 6);
+ spin_unlock_irqrestore(&skb_release_data_lock, flg);
if (skb_zcopy(skb)) {
bool skip_unref = shinfo->flags & SKBFL_MANAGED_FRAG_REFS;
--
next prev parent reply other threads:[~2024-12-18 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 17:03 [syzbot] [net?] general protection fault in put_page (4) syzbot
2024-12-17 17:06 ` Eric Dumazet
2024-12-18 18:06 ` Matthieu Baerts
2024-12-19 9:59 ` Aleksandr Nogikh
2024-12-19 15:53 ` Matthieu Baerts
2024-12-18 11:41 ` Hillf Danton
2024-12-18 11:55 ` syzbot
2024-12-18 23:14 ` Hillf Danton [this message]
2024-12-19 0:26 ` syzbot
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=20241218231457.288-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+38a095a81f30d82884c1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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