From: Jan Kara <jack@suse.cz>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Jan Kara <jack@suse.cz>,
stable@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3 STABLE] udf: Do not crash on corrupted media
Date: Mon, 9 Jul 2012 09:57:30 +0200 [thread overview]
Message-ID: <20120709075730.GA7564@quack.suse.cz> (raw)
In-Reply-To: <1341793325.25597.261.camel@deadeye.wl.decadent.org.uk>
On Mon 09-07-12 01:22:05, Ben Hutchings wrote:
> On Wed, 2012-07-04 at 13:01 +0200, Jan Kara wrote:
> > 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).
>
> All submissions to stable should include an upstream commit reference,
> but it looks like these are:
>
> cb14d34 udf: Use 'ret' instead of abusing 'i' in udf_load_logicalvol()
> adee11b udf: Avoid run away loop when partition table length is corrupted
> 1df2ae3 udf: Fortify loading of sparing table
Yes. Sorry for messing this up. I had the references there but git
send-email hid them in mail headers...
> I found that they apply to 3.2 without the logging change needed for
> 3.0, so I've added them to the queue as-is.
Great thanks.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-07-09 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 11:01 [PATCH 0/3 STABLE] udf: Do not crash on corrupted media Jan Kara
2012-07-04 11:01 ` [PATCH 1/3] udf: Use 'ret' instead of abusing 'i' in udf_load_logicalvol() Jan Kara
2012-07-04 11:01 ` [PATCH 2/3] udf: Avoid run away loop when partition table length is corrupted Jan Kara
2012-07-04 11:01 ` [PATCH 3/3] udf: Fortify loading of sparing table Jan Kara
2012-07-04 14:47 ` [PATCH 0/3 STABLE] udf: Do not crash on corrupted media Greg KH
2012-07-09 0:22 ` Ben Hutchings
2012-07-09 7:57 ` Jan Kara [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-04 10:55 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=20120709075730.GA7564@quack.suse.cz \
--to=jack@suse.cz \
--cc=ben@decadent.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.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).