From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Sergey S. Kostyliov" <rathamahata@php4.ru>
Cc: Will Dyson <will_dyson@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] befs (1/5): LBD support
Date: Fri, 14 May 2004 18:33:55 +0200 [thread overview]
Message-ID: <20040514163355.GC23863@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200405142009.36776.rathamahata@php4.ru>
On Fri, 14 May 2004 20:09:36 +0400, Sergey S. Kostyliov wrote:
> On Friday 14 May 2004 19:22, Will Dyson wrote:
> >
> > Are you interested in taking over official maintainership?
>
> Yes, I am interested. How do you like this patch?
Good to know. How do you like this patch?
Jörn
--
A quarrel is quickly settled when deserted by one party; there is
no battle unless there be two.
-- Seneca
Simply thinko:
inode->i_flags should never contain fs-specific flags. In fact, it doesn't;
the checks against it cause "chattr +T" to be useless for ext[23]. Same
bug was in befs as well.
linuxvfs.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.5cow/fs/befs/linuxvfs.c~befs_inode_flags 2004-04-27 16:34:51.000000000 +0200
+++ linux-2.6.5cow/fs/befs/linuxvfs.c 2004-04-27 16:48:54.000000000 +0200
@@ -376,7 +376,7 @@
befs_ino->i_attribute = fsrun_to_cpu(sb, raw_inode->attributes);
befs_ino->i_flags = fs32_to_cpu(sb, raw_inode->flags);
- if (S_ISLNK(inode->i_mode) && !(inode->i_flags & BEFS_LONG_SYMLINK)) {
+ if (S_ISLNK(inode->i_mode) && !(befs_ino->i_flags & BEFS_LONG_SYMLINK)){
inode->i_size = 0;
inode->i_blocks = befs_sb->block_size / VFS_BLOCK_SIZE;
strncpy(befs_ino->i_data.symlink, raw_inode->data.symlink,
next prev parent reply other threads:[~2004-05-14 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 18:32 Sergey S. Kostyliov
2004-05-14 2:16 ` Andrew Morton
2004-05-14 13:00 ` Sergey S. Kostyliov
2004-05-14 15:22 ` Will Dyson
2004-05-14 16:09 ` Sergey S. Kostyliov
2004-05-14 16:33 ` Will Dyson
2004-05-14 16:33 ` Jörn Engel [this message]
2004-05-14 16:58 ` Sergey S. Kostyliov
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=20040514163355.GC23863@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@php4.ru \
--cc=will_dyson@pobox.com \
/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®