From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v5, 03/16] ext4: Do not crash when trying to grow a directory using extents
Date: Fri, 23 Sep 2016 15:56:56 -0400 [thread overview]
Message-ID: <20160923195656.GG4884@bill-the-cat> (raw)
In-Reply-To: <c002ceffecb54a19becbf17f64e5b950@rwthex-w2-b.rwth-ad.de>
On Tue, Sep 06, 2016 at 04:36:43AM +0200, Stefan Br?ns wrote:
> The following command crashes u-boot:
> ./sandbox/u-boot -c 'i=0; host bind 0 ./sandbox/test/fs/3GB.ext4.img ;
> while test $i -lt 200 ; do echo $i; setexpr i $i + 1;
> ext4write host 0 0 /foobar${i} 0; done'
>
> Previously, the code updated the direct_block even for extents, and
> fortunately crashed before pushing garbage to the disk.
>
> Signed-off-by: Stefan Br?ns <stefan.bruens@rwth-aachen.de>
> Reviewed-by: Lukasz Majewski <l.majewski@samsung.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160923/c54b95ae/attachment-0001.sig>
next prev parent reply other threads:[~2016-09-23 19:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160906023656.13421-1-stefan.bruens@rwth-aachen.de>
2016-09-06 2:36 ` [U-Boot] [PATCH v5 01/16] ext4: fix possible crash on directory traversal, ignore deleted entries Stefan Brüns
2016-09-23 19:56 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 02/16] ext4: propagate error if creation of directory entry fails Stefan Brüns
2016-09-23 19:56 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 03/16] ext4: Do not crash when trying to grow a directory using extents Stefan Brüns
2016-09-23 19:56 ` Tom Rini [this message]
2016-09-06 2:36 ` [U-Boot] [PATCH v5 04/16] ext4: Scan all directory blocks for space when inserting a new entry Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 05/16] ext4: Avoid corruption of directories with hash tree indexes Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 06/16] ext4: Scan all directory blocks when looking up an entry Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 07/16] ext4: Only update number of of unused inodes if GDT_CSUM feature is set Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 08/16] ext4: Do not clear zalloc'ed buffers a second time Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 09/16] ext4: After completely filled group, scan next group from the beginning Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 10/16] ext4: Avoid out-of-bounds access of block bitmap Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 11/16] ext4: Fix memory leak in case of failure Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 12/16] ext4: Use correct value for inode size even on revision 0 filesystems Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 13/16] ext4: initialize full inode for inodes bigger than 128 bytes Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 14/16] ext4: remove duplicated block release code for extents Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 15/16] ext4: Correct block number handling, empty block vs. error code Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
2016-09-06 2:36 ` [U-Boot] [PATCH v5 16/16] ext4: Fix memory leak of journal buffer if block is updated multiple times Stefan Brüns
2016-09-23 19:57 ` [U-Boot] [U-Boot, v5, " Tom Rini
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=20160923195656.GG4884@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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