From: Lightweight patch manager <patch@luckynet.dynu.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, "H. Peter Avin" <hpa@zytor.com>
Subject: [PATCH][2.5] isofs: no unhide support any more
Date: Mon, 3 Jun 2002 17:38:05 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0206031735450.11309-100000@hawkeye.luckynet.adm> (raw)
This patch drops the unhide checks from dir.c and namei.c in isofs.
I don't know if this is the right approach, but that's at least what was
requested.
--- linux-2.5.20/fs/isofs/namei.c Sun Jun 2 19:44:52 2002
+++ thunder-2.5.20/fs/isofs/namei.c Mon Jun 3 17:27:38 2002
@@ -139,20 +139,8 @@
dpnt = tmpname;
}
- /*
- * Skip hidden or associated files unless unhide is set
- */
- match = 0;
- if (dlen > 0 &&
- (!(de->flags[-sbi->s_high_sierra] & 5)
- || sbi->s_unhide == 'y'))
- {
- match = (isofs_cmp(dentry,dpnt,dlen) == 0);
- }
- if (match) {
- if (bh) brelse(bh);
- return inode_number;
- }
+ if (bh) brelse(bh);
+ return inode_number;
}
if (bh) brelse(bh);
return 0;
--- linux-2.5.20/fs/isofs/dir.c Sun Jun 2 19:44:45 2002
+++ thunder-2.5.20/fs/isofs/dir.c Mon Jun 3 17:32:30 2002
@@ -192,16 +192,6 @@
continue;
}
- /* Handle everything else. Do name translation if there
- is no Rock Ridge NM field. */
- if (sbi->s_unhide == 'n') {
- /* Do not report hidden or associated files */
- if (de->flags[-sbi->s_high_sierra] & 5) {
- filp->f_pos += de_len;
- continue;
- }
- }
-
map = 1;
if (sbi->s_rock) {
len = get_rock_ridge_filename(de, tmpname, inode);
--
Lightweight patch manager using pine. If you have any objections, tell me.
reply other threads:[~2002-06-03 23:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.44.0206031735450.11309-100000@hawkeye.luckynet.adm \
--to=patch@luckynet.dynu.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--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;
as well as URLs for NNTP newsgroup(s).