From: "Eric Van Hensbergen" <eric.vanhensbergen@linux.dev>
To: asmadeus@codewreck.org, linux_oss@crudebyte.com,
lucho@ionkov.net, v9fs@lists.linux.dev
Subject: Re: [syzbot] [v9fs?] WARNING in v9fs_init_request
Date: Tue, 02 Apr 2024 01:41:14 +0000 [thread overview]
Message-ID: <971365953aa75ae614edb5a22a73b72f5eff7700@linux.dev> (raw)
In-Reply-To: <000000000000c6ea9b06150b361c@google.com>
April 1, 2024 at 11:09 AM, "syzbot" <syzbot+0354394655e838206fba@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 8d025e2092e2 Merge tag 'erofs-for-6.9-rc2-fixes' of git://..
>
> git tree: upstream
>
> console output: https://syzkaller.appspot.com/x/log.txt?x=17cb6d7e180000
>
> kernel config: https://syzkaller.appspot.com/x/.config?x=a2fbd4c518bbb6b3
>
> dashboard link: https://syzkaller.appspot.com/bug?extid=0354394655e838206fba
>
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> userspace arch: i386
^^^^
Seems like my concerns of my new inode handling on 32-bit architectures were valid.
Ugh, I suppose we could look at special casing 32-bit architectures to use the
longer qid.path evaluation logic and seperate i_ino allocation (which means inode
on client won't be the same as inodes on the server). Will try and come up with
a fix for this later this week.
-eric
prev parent reply other threads:[~2024-04-02 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 16:09 [syzbot] [v9fs?] WARNING in v9fs_init_request syzbot
2024-04-02 1:41 ` Eric Van Hensbergen [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=971365953aa75ae614edb5a22a73b72f5eff7700@linux.dev \
--to=eric.vanhensbergen@linux.dev \
--cc=asmadeus@codewreck.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=v9fs@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.