mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luca Tettamanti <kronos.it@gmail.com>
To: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
Cc: ismail@pardus.org.tr, linux-kernel@vger.kernel.org
Subject: Re: Linux ISO-9660 Rock Ridge bug needs fix
Date: Tue, 17 Oct 2006 21:50:22 +0200	[thread overview]
Message-ID: <20061017195022.GA23792@dreamland.darkstar.lan> (raw)
In-Reply-To: <45351de7.ky2ldiUVUFoikxQ6%Joerg.Schilling@fokus.fraunhofer.de>

Il Tue, Oct 17, 2006 at 08:16:07PM +0200, Joerg Schilling ha scritto: 
> Ismail Donmez <ismail@pardus.org.tr> wrote:
> 
> > I was just trying a fast hack to see it works ;-) but iso files produced by 
> > latest mkisofs works fine even without patching.
> 
> Did you _really_ use the latest mkisofs?

Yes, of course. As I said, the size of PX record is different:

000b820: 0100 5350 0701 beef 0052 5205 0181 5058  ..SP.....RR...PX
000b830: 2c01 6d41 0000 0000 416d 0200 0000 0000  ,.mA....Am......
         ^^ size is 44

but isofs (I'm using 2.6.19-rc2) doesn't care. If I'm reading the code
correctly record size is validated against (dentry size - name len -
records already parsed); it may be possibile to trigger the failure with
a certain combination of records (directory relocation?).
With my patch it should never happens that expected attributes size is
greater than dentry size.
Anyway, if you have a (small) image that triggers the error I can double
check the code.


Luca
-- 
#include <stdio.h> 
int main(void) {printf("\t\t\b\b\b\b\b\b");
printf("\t\t\b\b\b\b\b\b");return 0;}

  parent reply	other threads:[~2006-10-17 19:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 14:45 Joerg Schilling
2006-10-17 17:41 ` Ismail Donmez
2006-10-17 18:02   ` Luca Tettamanti
2006-10-17 18:14     ` Ismail Donmez
2006-10-17 18:16       ` Joerg Schilling
2006-10-17 18:32         ` Ismail Donmez
2006-10-17 19:50         ` Luca Tettamanti [this message]
2006-10-17 19:38     ` Pekka Enberg
2006-10-19 21:31       ` H. Peter Anvin
2006-10-17 18:12   ` Joerg Schilling
2006-10-17 18:28     ` Ismail Donmez
2006-10-17 18:32       ` Joerg Schilling
2006-10-17 18:39         ` Ismail Donmez
2006-10-17 21:07         ` James Lamanna
2006-10-17 21:32           ` Joerg Schilling
2006-10-17 21:51             ` James Lamanna
2006-10-17 22:24               ` Joerg Schilling
2006-10-17 23:06                 ` Alan Cox
2006-10-18 15:07                 ` Joerg Schilling
2006-10-17 19:53       ` Jan Engelhardt
2006-10-17 18:37 ` James Lamanna
     [not found] <771eN-VK-9@gated-at.bofh.it>
     [not found] ` <771yn-1XU-65@gated-at.bofh.it>
2006-10-17 23:09   ` Bodo Eggert
2006-10-18 15:14     ` Joerg Schilling
2006-10-18 22:45       ` Bodo Eggert
2006-10-18 23:29         ` Joerg Schilling
2006-10-19 21:16           ` Bodo Eggert
2006-10-19 21:39             ` Joerg Schilling
2006-10-19 21:49               ` Alan Cox

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=20061017195022.GA23792@dreamland.darkstar.lan \
    --to=kronos.it@gmail.com \
    --cc=Joerg.Schilling@fokus.fraunhofer.de \
    --cc=ismail@pardus.org.tr \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®