similar to: [2.6 patch] fs/ext3/: small cleanups

Can anyone tell me the history of CONFIG_EXT{2,3}_CHECK? There is code for a "check" option for mount if these options are enabled, but there's no way to enable them. TIA Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

Hello anybody, I have a Suse 7.2 Linux with Kernel 2.4.9, which is compiled by myself, and is running stable. Now I try to patch my sourcecode in the way you write on your homepage. But thier are two Proglems: 1. When I download the the file "ext3-2.4-0.9.6-249.gz" with my Windows, I get no packedfile, I get a Textfile?! -so gunzip would not work. 2. never the less, I tried to patch

Hi ! Is a ext3 patch for kernel 2.4.14pre7 available ? Patching 2.4.14pre7 with latest patch ext3-2.4-0.9.14-2414p5 fails: patching file include/linux/sched.h Hunk #2 succeeded at 489 (offset 1 line). patching file include/linux/fs.h patching file include/linux/capability.h patching file fs/buffer.c patching file mm/filemap.c Hunk #1 succeeded at 209 (offset 4 lines). patching file mm/vmscan.c

The patch below makes some needlessly global functions static. diffstat output: fs/smbfs/inode.c | 2 +- fs/smbfs/proc.c | 6 +++--- fs/smbfs/proto.h | 5 ----- fs/smbfs/request.c | 6 ++++-- 4 files changed, 8 insertions(+), 11 deletions(-) Signed-off-by: Adrian Bunk <bunk@stusta.de> --- linux-2.6.10-mm1-full/fs/smbfs/proto.h.old 2005-01-04 00:57:42.000000000 +0100

The patch below contains the following cleanups: - make some needlessly global code static - super.c: remove the unused global function ext3_panic Please comment ib whether this patch is correct or conflicts with pending changes. diffstat output: fs/ext3/balloc.c | 2 fs/ext3/dir.c | 2 fs/ext3/inode.c | 4 fs/ext3/resize.c | 4

This patch contains the following cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL: - journal.c: journal_recover Signed-off-by: Adrian Bunk

A couple of years ago there was a discussion on lkml under the thread 'PATCH - ext2fs privacy (i.e. secure deletion) patch' about zapping deleted data in the filesystem as a security mechanism. The discussion wandered off into how 'chattr +s' could be implemented and whether encrypting filesystems wouldn't be a better solution to the problem. I've been maintaining a

Al writes: > On Thu, 22 Mar 2001, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's

Hi Stephen, I'm one of developers of SnapFS, which based on Ext3. I got Assertion failure from SnapFS, at ext3_new_block() in fs/ext3/balloc.c: J_ASSERT (!test_and_set_bit(BH_Alloced, &bh->b_state)) If J_ASSERT is only use as debug, why it will modify data? I found the 'BH_Alloced' flag only occures at two place: one is balloc.c as above, the other is at journal_forget() in

Every file should include the headers containing the prototypes for its global functions. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- --- linux-2.6.22-rc6-mm1/arch/i386/xen/events.c.old 2007-07-03 04:26:28.000000000 +0200 +++ linux-2.6.22-rc6-mm1/arch/i386/xen/events.c 2007-07-03 04:26:59.000000000 +0200 @@ -31,6 +31,7 @@ #include <asm/irq.h> #include <asm/sync_bitops.h>

BRIDGE_EBT_ARPREPLY=y and INET=n results in the following compile error: <-- snip --> ... LD .tmp_vmlinux1 net/built-in.o: In function `ebt_target_reply': ebt_arpreply.c:(.text+0x68fb9): undefined reference to `arp_send' make: *** [.tmp_vmlinux1] Error 1 <-- snip --> Signed-off-by: Adrian Bunk <bunk@stusta.de> ---

This patch contains the following possible cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features -

This patch implements functions and timer setup which handles periodic syncing of locally cached quota information to global quota file. Signed-off-by: Jan Kara <jack at suse.cz> --- fs/ocfs2/quota.h | 3 ++ fs/ocfs2/quota_global.c | 66 +++++++++++++++++++++++++++++++++++++++++++++++ fs/ocfs2/quota_local.c | 4 +++ 3 files changed, 73 insertions(+), 0 deletions(-) diff

Hi, in the past I was considering the ways to back up files in my Linux home box. The important part of such thinking is how to set exclusion paths wisely. I finally found out that setting ext2/ext3 nodump attribute using chattr for files, but mainly directories, suits me best. Setting the match (regexp) lists for the backup script exetrnally seems sub-optimal to me, since my dump/nodump data

Description: Use schedule_timeout_{,un}interruptible() instead of set_current_state()/schedule_timeout() to reduce kernel size. Also use helper functions to convert between human time units and jiffies rather than constant HZ division to avoid rounding errors. Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com> --- fs/cifs/cifsfs.c | 7 ++----- fs/cifs/connect.c

This fixes the "i_blocks went wrong when the disk filled up" problem. In ext3_new_block() we increment i_blocks early, so the quota operation can be performed outside lock_super(). But if the block allocation ends up failing, we forget to undo the allocation. This is not a serious bug, and probably does not warrant an upgrade for production machines. Its effects are: 1) errors are

The patch forwarded below still applies against 2.6.10-mm2. Please apply. ----- Forwarded message from Adrian Bunk <bunk@stusta.de> ----- Date: Sun, 19 Dec 2004 14:58:37 +0100 From: Adrian Bunk <bunk@stusta.de> To: samba@samba.org Cc: linux-kernel@vger.kernel.org Subject: [2.6 patch] remove outdated smbfs ChangeLog The patch below removes an outdated samba ChangeLog file.

[Re-sending to the ext3 list, with minor edits] I'm in the process of fixing errors generated by the Coverity tool on the Linux kernel, and I would like your comment on a set of problems reported in ext3. The main issue reported is not checking the return code of ext3_journal_get_write_access() in various places. I would like to know if there should be error handling in these cases. The

Mzabalazo Ngwenya wrote: > Hi everyone ! > > I'm am trying to fit a kriging model to a set of data. When I just run > the "likfit" command I can obtain the results. However when I try to > pass additional arguements to the optimization function "optim" I get > errors. That is I want to obtain the hessian matrix so matrix > (hessian=TRUE). >

I've been working on a patchset to change how the inode->i_ctime is accessed in order to give us conditional, high-res timestamps for the ctime and mtime. struct timespec64 has unused bits in it that we can use to implement this. In order to do that however, we need to wrap all accesses of inode->i_ctime to ensure that bits used as flags are appropriately handled. This patchset first