linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: stable@kernel.org
Cc: <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/3 STABLE] udf: Do not crash on corrupted media
Date: Wed,  4 Jul 2012 12:55:15 +0200	[thread overview]
Message-ID: <1341399318-13744-1-git-send-email-jack@suse.cz> (raw)


  Hi,

  these patches went upstream recently and they improve UDF handling of
corrupted media. These patches are adjusted to work with 3.0 kernel (udf_err()
is called udf_error() in that kernel).

								Honza

             reply	other threads:[~2012-07-04 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 10:55 Jan Kara [this message]
2012-07-04 10:55 ` [PATCH 1/3] udf: Use 'ret' instead of abusing 'i' in udf_load_logicalvol() Jan Kara
2012-07-04 10:55 ` [PATCH 2/3] udf: Avoid run away loop when partition table length is corrupted Jan Kara
2012-07-04 10:55 ` [PATCH 3/3] udf: Fortify loading of sparing table Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2012-07-04 11:01 [PATCH 0/3 STABLE] udf: Do not crash on corrupted media Jan Kara
2012-07-04 14:47 ` Greg KH
2012-07-09  0:22 ` Ben Hutchings
2012-07-09  7:57   ` Jan Kara

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=1341399318-13744-1-git-send-email-jack@suse.cz \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=stable@kernel.org \
    /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).