similar to: Zeroing freed blocks

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.

Currently, default behavior of O_DIRECT writes was allowing concurrent writing among nodes, no cluster coherency guaranteed (no EX locks was taken), it hurts buffered reads on other nodes by reading stale data from cache. The new mount option introduce a chance to choose two different behaviors for O_DIRECT writes: * coherency=full, as the default value, will disallow concurrent

Hi, I have exactly the same problem that you experienced in Nov, 2013. I am using ext4 with journaled quota and the quota usage is only updating when I run quotacheck manually. Have you found a solution? Regards, Alex > I have set up user quotas on an ext4 filesystem. It does not appear that > the quota system is being updated, except when I manually run quotacheck. > > More detail:

I have set up user quotas on an ext4 filesystem. It does not appear that the quota system is being updated, except when I manually run quotacheck. More detail: I run "warnquota -s" from a script in /etc/cron.daily. I noticed that no one had received an "over quota" message in a long time. Using "repquota -as", it indeed looked as though everyone was under their

I have an ext4 filesystem for which I'm trying to use "tune2fs -l". Here is the listing of the filesystem from the "mount" command: # mount | grep share /dev/mapper/VolGroup_Share-LogVol_Share on /share type ext4 (rw,noatime,nodiratime,usrjquota=aquota.user,jqfmt=vfsv0,data=writeback,nobh,barrier=0) When I try to run "tune2fs" on it, I get the following error:

I starting seeing this error quite frequently the past couple of days: $ rake routes ruby(38294,0x7fff70ee6ca0) malloc: *** error for object 0x100000000: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Abort trap Rails server crashes, some rake tasks crash, but not consistently. I have: - removed ruby 1.9.2-p180 and reinstalled (via rvm) - delete gemset

the memory which is allocated by matchpathcon should be freed after it is useless Signed-off-by: Roy Li <rongqing.li at windriver.com> --- openbsd-compat/port-linux.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --- a/openbsd-compat/port-linux.c +++ b/openbsd-compat/port-linux.c @@ -217,8 +217,10 @@ ssh_selinux_setfscreatecon(const char *p setfscreatecon(NULL);

Hi, My Xen 3.2 does not boot. Its stuck at "Freeing unused kernel memory: 148k freed". I used a FC8 distribution from jailtime.org. My kernel is built using make KERNELS= # xm console src-fc-01 xen-vbd: registered block device major 8 blkfront: sda1: barriers enabled blkfront: sda2: barriers enabled netfront: Initialising virtual ethernet driver. vif vif-0: 2 parsing device/vif/0/mac

I have started rewriting the ioctl#21 patch using a less hacky architecture, including defining a new kind of structure that explicitly organizes information common to delayed/deferred systems, (the list of work pieces, and an atomic for counting active worker threads) and replacing the lists of work pieces, in ioctl#21-tracked deferred systems, with this structure instead. I started march 25,

Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/core/handle.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/core/core/handle.c b/drivers/gpu/drm/nouveau/core/core/handle.c index b8d2cbf..264c2b3 100644 --- a/drivers/gpu/drm/nouveau/core/core/handle.c +++

From: Raushaniya Maksudova <rmaksudova at parallels.com> This value would be useful in the next patch to provide the amount of the freed memory for OOM killer. Signed-off-by: Raushaniya Maksudova <rmaksudova at parallels.com> Signed-off-by: Denis V. Lunev <den at openvz.org> CC: Rusty Russell <rusty at rustcorp.com.au> CC: Michael S. Tsirkin <mst at redhat.com> ---

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=86 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Summary|using freed skb in |using

https://bugzilla.mindrot.org/show_bug.cgi?id=1962 Bug #: 1962 Summary: command buffer struct is not freed before exit() Classification: Unclassified Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: ssh

https://bugzilla.mindrot.org/show_bug.cgi?id=1962 --- Comment #2 from Loganaden Velvindron <loganaden at gmail.com> --- Upon discussion with openbsd folks on irc, most modern Unix out there free it automatically upon exit. We can close the ticket right ? -- You are receiving this mail because: You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=1962 Loganaden Velvindron <loganaden at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Loganaden

https://bugzilla.mindrot.org/show_bug.cgi?id=1962 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Damien Miller <djm at mindrot.org> --- Set all RESOLVED bugs to CLOSED with release

free_last_match() frees the memory of the match passed as argument, so accessing it is not possible after free_last_match(). Since all we need is the return code, save it locally for later usage. --- common/mlpcre/pcre-c.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/common/mlpcre/pcre-c.c b/common/mlpcre/pcre-c.c index da982025f..0762a8341 100644 ---

Hello, there is a small bug in mingw/device.c : After freeing the addrinfo structure there are further accesses to members of the structure. I discovered this bug while using this code unter MS Visual Studio. ------ freeaddrinfo(ai); if(sock < 0) { logger(LOG_ERR, _("System call `%s' failed: %s"), "socket", strerror(errno)); return -1; } if(connect(sock,

[PATCH] virtio_net: Delay dropping tx skbs Cc: Mark McLoughlin <markmc at redhat.com>, virtualization at lists.linux-foundation.org, netdev at vger.kernel.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807151340.00446.rusty at rustcorp.com.au> From: Mark McLoughlin <markmc at redhat.com> On Mon, 2008-05-26 at 17:42 +1000,

[PATCH] virtio_net: Delay dropping tx skbs Cc: Mark McLoughlin <markmc at redhat.com>, virtualization at lists.linux-foundation.org, netdev at vger.kernel.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807151340.00446.rusty at rustcorp.com.au> From: Mark McLoughlin <markmc at redhat.com> On Mon, 2008-05-26 at 17:42 +1000,