mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+97bf275720e06ad75f63@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in rt_set_nexthop
Date: Sat, 12 Jul 2025 09:18:55 +0800	[thread overview]
Message-ID: <20250712011856.3599-1-hdanton@sina.com> (raw)
In-Reply-To: <6871b125.a00a0220.26a83e.0066.GAE@google.com>

> Date: Fri, 11 Jul 2025 17:49:41 -0700	[thread overview]
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    d7b8f8e20813 Linux 6.16-rc5
> git tree:       upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=107f9582580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=f6cfc97245100778
> dashboard link: https://syzkaller.appspot.com/bug?extid=97bf275720e06ad75f63
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17b6728c580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12aac28c580000

#syz test upstream  master

--- x/net/rxrpc/call_accept.c
+++ y/net/rxrpc/call_accept.c
@@ -348,7 +348,7 @@ bool rxrpc_new_incoming_call(struct rxrp
 	if (sp->hdr.type != RXRPC_PACKET_TYPE_DATA)
 		return rxrpc_protocol_error(skb, rxrpc_eproto_no_service_call);
 
-	read_lock_irq(&local->services_lock);
+	read_lock_bh(&local->services_lock);
 
 	/* Weed out packets to services we're not offering.  Packets that would
 	 * begin a call are explicitly rejected and the rest are just
@@ -405,7 +405,7 @@ bool rxrpc_new_incoming_call(struct rxrp
 	spin_unlock(&conn->state_lock);
 
 	spin_unlock(&rx->incoming_lock);
-	read_unlock_irq(&local->services_lock);
+	read_unlock_bh(&local->services_lock);
 
 	if (hlist_unhashed(&call->error_link)) {
 		spin_lock_irq(&call->peer->lock);
@@ -419,20 +419,20 @@ bool rxrpc_new_incoming_call(struct rxrp
 	return true;
 
 unsupported_service:
-	read_unlock_irq(&local->services_lock);
+	read_unlock_bh(&local->services_lock);
 	return rxrpc_direct_abort(skb, rxrpc_abort_service_not_offered,
 				  RX_INVALID_OPERATION, -EOPNOTSUPP);
 unsupported_security:
-	read_unlock_irq(&local->services_lock);
+	read_unlock_bh(&local->services_lock);
 	return rxrpc_direct_abort(skb, rxrpc_abort_service_not_offered,
 				  RX_INVALID_OPERATION, -EKEYREJECTED);
 no_call:
 	spin_unlock(&rx->incoming_lock);
-	read_unlock_irq(&local->services_lock);
+	read_unlock_bh(&local->services_lock);
 	_leave(" = f [%u]", skb->mark);
 	return false;
 discard:
-	read_unlock_irq(&local->services_lock);
+	read_unlock_bh(&local->services_lock);
 	return true;
 }
 
--

  reply	other threads:[~2025-07-12  1:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-12  0:49 syzbot
2025-07-12  1:18 ` Hillf Danton [this message]
2025-07-12  3:06   ` syzbot
2025-08-08 21:53 ` 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=20250712011856.3599-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+97bf275720e06ad75f63@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

all inboxes | Powered by JetHome®