Re: [PATCH 3/3] ext4: correctly handle a zero-length xattr with a non-zero e_value_offs

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

To: Andreas Dilger <adilger@xxxxxxxxx>
Subject: Re: [PATCH 3/3] ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
Date: Thu, 24 May 2018 21:29:16 -0400
Cc: Ext4 Developers List <linux-ext4@xxxxxxxxxxxxxxx>, wen.xu@xxxxxxxxxx, jannh@xxxxxxxxxx
In-reply-to: <43DC61AD-22BC-4842-81F7-C50FB7B0C163@dilger.ca>
References: <20180523153714.28470-1-tytso@mit.edu> <20180523153714.28470-3-tytso@mit.edu> <43DC61AD-22BC-4842-81F7-C50FB7B0C163@dilger.ca>
User-agent: Mutt/1.9.5 (2018-04-13)

Thanks, good point, I'll cut down the kernel BUG meussage, especially
since the full message can be found in the kernel bugzilla.

      	       	       	      	    - Ted

References:
- [PATCH 1/3] ext4: do not allow external inodes for inline data
  - From: Theodore Ts'o
- [PATCH 3/3] ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
  - From: Theodore Ts'o
- Re: [PATCH 3/3] ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
  - From: Andreas Dilger

Prev by Date: [Bug 199347] buffer overflow in ext4_xattr_set_entry() when mounting and operating a crafted ext4 image
Next by Date: [PATCH v4 1/4] ext2fs: opening filesystem code refactoring
Previous by thread: Re: [PATCH 3/3] ext4: correctly handle a zero-length xattr with a non-zero e_value_offs
Next by thread: Re: [PATCH 1/3] ext4: do not allow external inodes for inline data
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux