linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: linux-fsdevel@vger.kernel.org, tyler.hicks@canonical.com
Subject: [PATCH 0/2] ecryptfs: Improved metadata read failure logging
Date: Wed, 11 Jan 2012 18:00:40 +0100	[thread overview]
Message-ID: <1326301242-5817-1-git-send-email-tim.gardner@canonical.com> (raw)

This patch set improves error logging when metadata read failures are
encountered. This is usually the result of lower file system corruption
or from an older inode race bug where 0 length FNEK files were created.


             reply	other threads:[~2012-01-11 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 17:00 Tim Gardner [this message]
2012-01-11 17:00 ` [PATCH 1/2] ecryptfs: Improve metatdata read failure logging Tim Gardner
2012-01-11 20:36   ` Kees Cook
2012-01-12 12:00   ` Tyler Hicks
2012-01-12 16:45     ` Tim Gardner
2012-01-20 19:50       ` Tyler Hicks
2012-01-20 20:17         ` Tim Gardner
2012-01-11 17:00 ` [PATCH 2/2] ecryptfs: Print inode on metadata error Tim Gardner
2012-01-11 20:38   ` Kees Cook
2012-01-12 12:02   ` Tyler Hicks

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=1326301242-5817-1-git-send-email-tim.gardner@canonical.com \
    --to=tim.gardner@canonical.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tyler.hicks@canonical.com \
    /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;
as well as URLs for NNTP newsgroup(s).