From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+e78eab0c1cf4649256ed@syzkaller.appspotmail.com>
Cc: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] WARNING in do_symlinkat
Date: Thu, 25 May 2023 12:01:10 +0200 [thread overview]
Message-ID: <CANp29Y68oXAQZBAChyiB58qebXS5bNOGda6tG=B+kKa7QRh6EQ@mail.gmail.com> (raw)
In-Reply-To: <0000000000000ca36b05fc780953@google.com>
On Thu, May 25, 2023 at 12:29 AM syzbot
<syzbot+e78eab0c1cf4649256ed@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 267a36ba30a7425ad59d20e7e7e33bbdcc9cfb0a
> Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
> Date: Mon Jan 16 08:52:10 2023 +0000
>
> fs/ntfs3: Remove noacsrules
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15fdf761280000
> start commit: ec35307e18ba Merge tag 'drm-fixes-2023-02-17' of git://ano..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=5f0b8e3df6f76ec
> dashboard link: https://syzkaller.appspot.com/bug?extid=e78eab0c1cf4649256ed
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12570890c80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14523acf480000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs/ntfs3: Remove noacsrules
This commit definitely removes one of the options used by the
reproducer, though at least from the stack trace it's not clear
whether the problem was in noacsrules or we're just now not mounting
the image because of invalid mount options.
Anyway, let's close the bug, it will reappear on syzbot if it's not fixed.
#syz fix: fs/ntfs3: Remove noacsrules
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
prev parent reply other threads:[~2023-05-25 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 2:46 [syzbot] [vfs?] [ntfs3?] WARNING in do_symlinkat syzbot
2022-12-27 20:13 ` syzbot
2023-05-24 22:29 ` [syzbot] " syzbot
2023-05-25 10:01 ` Aleksandr Nogikh [this message]
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='CANp29Y68oXAQZBAChyiB58qebXS5bNOGda6tG=B+kKa7QRh6EQ@mail.gmail.com' \
--to=nogikh@google.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+e78eab0c1cf4649256ed@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).