mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: syzbot <syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_write_single_data_page
Date: Thu, 4 May 2023 21:48:04 +0800	[thread overview]
Message-ID: <d6a26ad8-3c90-d932-d966-85414e0ae42a@kernel.org> (raw)
In-Reply-To: <00000000000032909d05fade30c8@google.com>

Hi,

On 2023/5/4 21:31, syzbot wrote:
> Hello,
> 
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:

It said the reproducer is still triggering an issue, however, there is
no error output from the test.

Could you please help to check whether such status is normal or not, or
am I missing something?

Thanks,

> no output from test machine
> 
> 
> 
> Tested on:
> 
> commit:         2adb872d f2fs: fix potential deadlock due to unpaired ..
> git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test
> console output: https://syzkaller.appspot.com/x/log.txt?x=114b5338280000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=86e4eb913e90d4b2
> dashboard link: https://syzkaller.appspot.com/bug?extid=eb6201248f684e99b9f8
> compiler:       Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
> 
> Note: no patches were applied.

  reply	other threads:[~2023-05-04 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 17:05 syzbot
2023-05-03 15:28 ` Chao Yu
2023-05-03 16:08   ` syzbot
2023-05-04 12:08 ` Chao Yu
2023-05-04 13:31   ` syzbot
2023-05-04 13:48     ` Chao Yu [this message]
2023-05-04 13:53       ` Aleksandr Nogikh
2023-09-15  5:49 ` syzbot
     [not found] <20230502015215.3335-1-hdanton@sina.com>
2023-05-02  2:33 ` 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=d6a26ad8-3c90-d932-d966-85414e0ae42a@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+eb6201248f684e99b9f8@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®