public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ismail Donmez <ismail@pardus.org.tr>
To: Joerg Schilling <schilling@fokus.fraunhofer.de>
Cc: linux-kernel@vger.kernel.org, Me@fokus.fraunhofer.de
Subject: Re: Linux ISO-9660 Rock Ridge bug needs fix
Date: Tue, 17 Oct 2006 20:41:41 +0300	[thread overview]
Message-ID: <200610172041.42873.ismail@pardus.org.tr> (raw)
In-Reply-To: <200610171445.k9HEji8R018455@burner.fokus.fraunhofer.de>

[-- Attachment #1: Type: text/plain, Size: 551 bytes --]

17 Eki 2006 Sal 17:45 tarihinde, Joerg Schilling şunları yazmıştı: 
> Hi,
>
> while working on better ISO-9660 support for the Solaris Kernel,
> I recently enhanced mkisofs to support the Rock Ridge Standard version 1.12
> from 1994.
>
> The difference bewteen version 1.12 and 1.10 (this is what previous
> mkisofs versions did implement) is that the "PX" field is now 8 Byte
> bigger than before (44 instead of 36 bytes).

Is there a test iso file somewhere? I think the attached *untested* patch will 
fix it.

Regards,
ismail

[-- Attachment #2: rock.patch --]
[-- Type: text/x-diff, Size: 644 bytes --]

diff --git a/fs/isofs/rock.c b/fs/isofs/rock.c
index f3a1db3..061a633 100644
--- a/fs/isofs/rock.c
+++ b/fs/isofs/rock.c
@@ -349,6 +349,7 @@ #endif
 			inode->i_nlink = isonum_733(rr->u.PX.n_links);
 			inode->i_uid = isonum_733(rr->u.PX.uid);
 			inode->i_gid = isonum_733(rr->u.PX.gid);
+                       inode->i_ino = isonum_733(rr->u.PX.ino);
 			break;
 		case SIG('P', 'N'):
 			{
diff --git a/fs/isofs/rock.h b/fs/isofs/rock.h
index ed09e2b..faf92c6 100644
--- a/fs/isofs/rock.h
+++ b/fs/isofs/rock.h
@@ -33,6 +33,7 @@ struct RR_PX_s {
 	char n_links[8];
 	char uid[8];
 	char gid[8];
+       char ino[8];
 };
 
 struct RR_PN_s {

  reply	other threads:[~2006-10-17 17:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 14:45 Linux ISO-9660 Rock Ridge bug needs fix Joerg Schilling
2006-10-17 17:41 ` Ismail Donmez [this message]
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
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=200610172041.42873.ismail@pardus.org.tr \
    --to=ismail@pardus.org.tr \
    --cc=Me@fokus.fraunhofer.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schilling@fokus.fraunhofer.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox