Re: WARNING in filldir64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Eric Biggers <ebiggers@xxxxxxxxxx>
Subject: Re: WARNING in filldir64
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 7 Oct 2019 12:24:19 -0700
Cc: syzbot <syzbot+3031f712c7ad5dd4d926@xxxxxxxxxxxxxxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, syzkaller-bugs <syzkaller-bugs@xxxxxxxxxxxxxxxx>, Al Viro <viro@xxxxxxxxxxxxxxxxxx>
In-reply-to: <20191007191918.GD16653@gmail.com>

On Mon, Oct 7, 2019 at 12:19 PM Eric Biggers <ebiggers@xxxxxxxxxx> wrote:
>
> So it seems to have generated a corrupt filesystem image and tried to mount it.

Ok, then everything is working as expected.

Let's ignore the syzbot one for now, and see if some other load triggers this.

             Linus

References:
- WARNING in filldir64
  - From: syzbot
- Re: WARNING in filldir64
  - From: Eric Biggers
- Re: WARNING in filldir64
  - From: Linus Torvalds
- Re: WARNING in filldir64
  - From: Eric Biggers

Prev by Date: Re: [PATCH] Convert filldir[64]() from __put_user() to unsafe_put_user()
Next by Date: Re: [PATCH] Convert filldir[64]() from __put_user() to unsafe_put_user()
Previous by thread: Re: WARNING in filldir64
Next by thread: WARNING in verify_dirent_name
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux