LKML Archive on
help / color / mirror / Atom feed
From: Linus Torvalds <>
To: kernel test robot <>,
	Konstantin Komarov <>
Cc: yangerkun <>,
	Al Viro <>,
	Andrew Morton <>,
	LKML <>,, kernel test robot <>
Subject: Re: [ramfs] 0858d7da8a: canonical_address#:#[##]
Date: Thu, 25 Nov 2021 10:03:33 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20211125140816.GC3109@xsang-OptiPlex-9020>

On Thu, Nov 25, 2021 at 6:08 AM kernel test robot <> wrote:
> FYI, we noticed the following commit (built with clang-14):
> commit: 0858d7da8a09e440fb192a0239d20249a2d16af8 ("ramfs: fix mount source show for ramfs")

Funky. That commit seems to have nothing to do with the oops:

> [  806.257788][  T204] /dev/root: Can't open blockdev
> [  806.259101][  T204] general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] SMP KASAN
> [  806.263082][  T204] KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]

Not a very helpful error message,a nd the KASAN comment makes little sense, but

> [ 806.267540][ T204] RIP: 0010:ntfs_update_mftmirr (kbuild/src/consumer/fs/ntfs3/fsntfs.c:834)


        u32 blocksize = sb->s_blocksize;

and presumably with KASAN you end up getting hat odd 0xdffffc0000000003 thing.

Anyway, looks like sb is NULL, and the code is

  int ntfs_update_mftmirr(struct ntfs_sb_info *sbi, int wait)
        int err;
        struct super_block *sb = sbi->sb;
        u32 blocksize = sb->s_blocksize;
        sector_t block1, block2;

although I have no idea how sbi->sb could be NULL.

Konstantin? See

for the full thing.


  reply	other threads:[~2021-11-25 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 14:08 kernel test robot
2021-11-25 18:03 ` Linus Torvalds [this message]
2021-11-26  1:54   ` yangerkun
2021-11-26 11:36     ` Kari Argillander

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \
    --subject='Re: [ramfs] 0858d7da8a: canonical_address#:#[##]' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).