[PATCH 0/2] Handle invalid os_type in e2p.

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

To: linux-ext4@xxxxxxxxxxxxxxx
Subject: [PATCH 0/2] Handle invalid os_type in e2p.
From: Adam Buchbinder <abuchbinder@xxxxxxxxxx>
Date: Tue, 18 Jul 2017 12:29:17 -0700

Hi! While fuzzing with american fuzzy lop, I discovered an issue in
the e2p library. The fix there seemed straightforward, but I'm not
sure I understand the testing infrastructure; running dumpe2fs looks
like the easiest way to trigger the problem. Any feedback here would
be welcome. Thanks!

Adam Buchbinder
Google, Inc.

Follow-Ups:
- [PATCH v2 0/2] Handle invalid os_type in e2p.
  - From: Adam Buchbinder
- [PATCH 2/2] e2p: Fix segfault in e2p_os2string.
  - From: Adam Buchbinder
- [PATCH 1/2] tests: dumpe2fs against an image with bad os_type.
  - From: Adam Buchbinder

Prev by Date: Re: Which kernel do I need to use ext4 64-bit.
Next by Date: [PATCH 1/2] tests: dumpe2fs against an image with bad os_type.
Previous by thread: PROBLEM: lseek64 to END on directory returns INT64_MAX
Next by thread: [PATCH 1/2] tests: dumpe2fs against an image with bad os_type.
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