mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: Chao Yu <chao@kernel.org>,
	syzbot+001306cd9c92ce0df23f@syzkaller.appspotmail.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] erofs: ensure regular inodes for file-backed mounts
Date: Fri, 11 Oct 2024 11:10:26 +0800	[thread overview]
Message-ID: <27aeda6c-dd0d-4cef-b071-18499b1b3e70@kernel.org> (raw)
In-Reply-To: <20240917130803.32418-1-hsiangkao@linux.alibaba.com>

On 2024/9/17 21:08, Gao Xiang wrote:
> Only regular inodes are allowed for file-backed mounts, not directories
> (as seen in the original syzbot case) or special inodes.
> 
> Also ensure that .read_folio() is implemented on the underlying fs
> for the primary device.
> 
> Fixes: fb176750266a ("erofs: add file-backed mount support")
> Reported-by: syzbot+001306cd9c92ce0df23f@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/r/00000000000011bdde0622498ee3@google.com
> Tested-by: syzbot+001306cd9c92ce0df23f@syzkaller.appspotmail.com
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

      reply	other threads:[~2024-10-11  3:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  4:59 [syzbot] [erofs?] [mm?] BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio (3) syzbot
2024-09-17  5:58 ` [PATCH] erofs: ensure regular inodes for file-backed mounts Gao Xiang
2024-09-17  6:39 ` [syzbot] [erofs?] [mm?] BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio (3) Gao Xiang
2024-09-17  7:02   ` syzbot
2024-09-17 13:08 ` [PATCH v2] erofs: ensure regular inodes for file-backed mounts Gao Xiang
2024-10-11  3:10   ` Chao Yu [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=27aeda6c-dd0d-4cef-b071-18499b1b3e70@kernel.org \
    --to=chao@kernel.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+001306cd9c92ce0df23f@syzkaller.appspotmail.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®