public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pengfei Xu <pengfei.xu@intel.com>
To: Alexander Wetzel <alexander@wetzel-home.de>
Cc: syzbot <syzbot+93cdc797590ffc710918@syzkaller.appspotmail.com>,
	<dgilbert@interlog.com>, <jejb@linux.ibm.com>,
	<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	<martin.petersen@oracle.com>, <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] [scsi?] WARNING in sg_remove_sfp_usercontext
Date: Sun, 7 Apr 2024 18:50:13 +0800	[thread overview]
Message-ID: <ZhJ6ZQc8KkOX01CW@xpf.sh.intel.com> (raw)
In-Reply-To: <0c2ee56a-13a6-4d93-8c45-f43f551bf1da@wetzel-home.de>

Hi Alexander,

On 2024-04-04 at 14:05:12 +0200, Alexander Wetzel wrote:
> On 04.04.24 12:57, Pengfei Xu wrote:
> > cc Alexander Wetzel,
> > 
> > I used syzkaller and found the similar problem.
> > 
> > And bisected and found the related commit:
> > 27f58c04a8f4 scsi: sg: Avoid sg device teardown race
> > Reverted the commit on top of v6.9-rc2, this issue was gone.
> 
> There were now multiple reports about the issue. The first (main) discussion
> and fix is here:
> https://lore.kernel.org/all/20240401191038.18359-1-Alexander@wetzel-home.de/
> 
> In a nutshell:
> The new WARN_ON_ONCE() was a (very) stupid idea and must be undone.
> It's ok to just drop the line with the WARN_ON_ONCE(). The rest of the
> proposed patch fixes a much less urgent issue.

  Got it, thanks for your description!

> 
> Of course I can also break the fix into two patches, when this speeds up the
> merge...

Thank you, if it makes sense and accelerates the merge process.

Best Regards,
Thanks1

> 
> Alexander

  reply	other threads:[~2024-04-07 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 14:31 [syzbot] [scsi?] WARNING in sg_remove_sfp_usercontext syzbot
2024-03-28 22:40 ` syzbot
2024-04-04 10:57   ` Pengfei Xu
2024-04-04 12:05     ` Alexander Wetzel
2024-04-07 10:50       ` Pengfei Xu [this message]
2024-05-18 19:54 ` Fedor Pchelkin

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=ZhJ6ZQc8KkOX01CW@xpf.sh.intel.com \
    --to=pengfei.xu@intel.com \
    --cc=alexander@wetzel-home.de \
    --cc=dgilbert@interlog.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=syzbot+93cdc797590ffc710918@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