All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/5] Enhance fs tests
Date: Wed, 14 Sep 2016 01:01:26 +0200	[thread overview]
Message-ID: <2fe9d0e19575419ca0c7457ac0e50747@rwthex-w2-b.rwth-ad.de> (raw)

The first 3 patches do some cleanups for the current test, especially TC11
had some issues (strange match for expected output, use of unitialized
variable).

The last two patches add test cases for handling ".". Ext4 used to crash,
as a match on the first entry of a directory block was not handled
correctly.

v2:
  Updated:
    test/fs: Restructure file path specification to allow some flexibility
      * avoid creation of paths with double slashes
    test/fs: Check writes using "." (same dir) relative path
      * fix issues copied from TC11
      * delete written file in cleanup
  Added:
    test/fs: remove use of undefined WRITE_FILE variable
    test/fs: strip noise from filesystem code prior to checking results

Stefan Br?ns (5):
  test/fs: Restructure file path specification to allow some flexibility
  test/fs: remove use of undefined WRITE_FILE variable
  test/fs: strip noise from filesystem code prior to checking results
  test/fs: Check ext4 behaviour if dirent is first entry in directory
    block
  test/fs: Check writes using "." (same dir) relative path

 test/fs/fs-test.sh | 131 +++++++++++++++++++++++++++++++----------------------
 1 file changed, 78 insertions(+), 53 deletions(-)

-- 
2.10.0

             reply	other threads:[~2016-09-13 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 23:01 Stefan Brüns [this message]
2016-09-14 13:32 ` [U-Boot] [PATCH v2 0/5] Enhance fs tests Simon Glass
2016-09-14 13:38   ` Tom Rini
2016-09-14 14:22     ` Simon Glass

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=2fe9d0e19575419ca0c7457ac0e50747@rwthex-w2-b.rwth-ad.de \
    --to=stefan.bruens@rwth-aachen.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.