Displaying 18 results from an estimated 18 matches similar to: "[patch 1/3] fs/ext3/super.c: fix sparse warnings"
2005 Feb 15
1
[PATCH] ext3: Fix sparse -Wbitwise warnings.
Signed-off-by: Alexey Dobriyan <adobriyan at mail.ru>
---
fs/ext3/resize.c | 20 ++++++++++----------
fs/ext3/super.c | 8 ++++----
include/linux/ext3_fs.h | 2 +-
3 files changed, 15 insertions(+), 15 deletions(-)
Index: linux-warnings/include/linux/ext3_fs.h
===================================================================
---
2005 Jun 20
0
[patch 3/3] Fix misleading gcc4 warning, size may be used uninitialized (ext3)
An embedded and charset-unspecified text was scrubbed...
Name: gcc4-fs_ext3_acl.c
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/80eb5460/attachment.c>
2005 Jun 20
0
[patch 2/3] fs/ext3/resize.c: fix sparse warnings
An embedded and charset-unspecified text was scrubbed...
Name: sparse-fs_ext3_resize.patch
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/8e33ffa8/attachment.ksh>
2005 Jan 06
0
[2.6 patch] fs/ext3/: possible cleanups
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
2002 Dec 24
0
Cosmetical printk change, remounting problems.
Hi!
I noticed yet another dying IBM drive in one of my servers, producing IDE
+ "standard" ext3 error messages (happened during the start of a new
journal methinks):
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device ide5(57,1)) in
ext3_reserve_inode_write: Journal has aborted
which clearly shows that
2001 Nov 20
1
EXT3-fs error (device ide0(3,9)): ext3_readdir
Hi,
yesterday I upgraded my kernel to 2.4.15-pre6 (after months of using
only ac-kernels) and had my first ext3-error since 0.0.3 .
syslog tells me :
Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device ide0(3,9)):
ext3_readdir: bad entry in directory #47390: inode out of bounds -
offset=0, inode=404363549, rec_len=4096, name_len=23
and the system remounted /usr to ro.
I don't have
2007 Mar 29
3
tune2fs -l stale info
Hello,
I just noticed that 'tune2fs -l' did not returned a "lively" updated
information regarding the free inodes count (looks like it's always
correct after unmounting). It became suprising after an online resizing
operation, where the total inode count was immediatly updated (grown in
my case) but the free inode count was the same: one could deduce that
suddenly a lot of
2002 Dec 06
2
[patch] fix the ext3 data=journal unmount bug
This patch fixes the data loss which can occur when unmounting a
data=journal ext3 filesystem.
The core problem is that the VFS doesn't tell the filesystem enough
about what is happening. ext3 _needs_ to know the difference between
regular memory-cleansing writeback and sync-for-data-integrity
purposes.
(These two operations are really quite distinct, and the kernel has got
it wrong for
2007 Mar 16
0
DISA and repeating calls
Hello,
I have a setup like this:
exten => s,1,Ringing
exten => s,n,Wait(3)
exten => s,n,Answer
exten => s,n,Set(TIMEOUT(digit)=6)
exten => s,n,Authenticate(11111)
exten => s,n,DISA(no-password|my-context)
exten => i,1,Playback(invalid)
exten => i,n,Wait(1)
exten => i,n,Goto(s,5)
exten => t,1,Hangup
I need to be able to get back to the
2023 Feb 07
1
[PATCH v2] x86/paravirt: merge activate_mm and dup_mmap callbacks
The two paravirt callbacks .mmu.activate_mm and .mmu.dup_mmap are
sharing the same implementations in all cases: for Xen PV guests they
are pinning the PGD of the new mm_struct, and for all other cases
they are a NOP.
In the end both callbacks are meant to register an address space with
the underlying hypervisor, so there needs to be only a single callback
for that purpose.
So merge them to a
2011 Sep 13
1
Quota fs (don't start script quota-warning.sh)
Hi,
# doveadm -Dv quota get -u pit
doveadm(pit): Debug: auth input: pit system_groups_user=pit uid=500 gid=500 home=/home/pit
doveadm(pit): Debug: Effective uid=500, gid=500, home=/home/pit
doveadm(pit): Debug: Quota root: name=INBOX backend=fs args=mount=/var/spool/mail
doveadm(pit): Debug: Quota rule: root=INBOX mailbox=* bytes=19922944 messages=0
doveadm(pit): Debug: Quota warning:
2006 May 26
1
[PATCH - 2.6.17-rc5] ext3: Fix missed mutex unlock - unroll
Hi,
I believe the following patch in the GIT - 2.6.17-rc5 is not correct:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=75616cf9854b83eb83a968b1338ae0ee11c9673c
It is the second of the two patches contributed by Leonid Ananiev. This
one incorrectly adds the super block unlocking in the error path, though.
As we can see in the function ext3_group_add() the
2015 Dec 18
0
[ANNOUNCE] iptables 1.6.0 release
Hi!
The Netfilter project proudly presents:
iptables 1.6.0
This release includes accumulated fixes and enhancements for the
following matches:
* ah
* connlabel
* cgroup
* devgroup
* dst
* icmp6
* ipcomp
* ipv6header
* quota
* set
* socket
* string
and targets:
* CT
* REJECT
* SET
* SNAT
* SNPT,DNPT
* SYNPROXY
* TEE
We also got rid of the very very old MIRROR and SAME targets and the
2013 Nov 06
2
HVM crash system on AMD APU A8-6600K
My system reboots when I trying to start any HVM domU. This problem
was described earlier:
http://lists.xen.org/archives/html/xen-devel/2013-08/msg01395.html
My system is openSUSE 13.1 RC2 with Xen 4.3.0
My hardware is
ASRock FM2A75 Pro4
AMD A8-6600K APU
Gigabyte Radeon 7850
8 Gb DDR3 1600Mhz
I have setup serial console and could provide logs your requested.
Attached logs from xl dmesg,
2011 Sep 06
3
Quota fs (ignore mount)
Hi,
I set "quota: fs:INBOX:noenforcing:mount=/var/spool/mail", but receive: "fs quota add storage dir = /home/pit/mail"...
Why ?
In fstab:
/dev/mapper/mpath1p1 /var/spool/mail ext2 usrquota 0 0
In dovecot.log:
Sep 06 15:02:00 pop3-login: Info: Login: user=<pit>, method=PLAIN, rip=192.168.3.10, lip=192.168.6.3, TLS
Sep 06 15:02:00 POP3(pit): Info: Loading modules
2020 Feb 19
5
[PATCH 04/12] drm: Nuke mode->vrefresh
From: Ville Syrj?l? <ville.syrjala at linux.intel.com>
Get rid of mode->vrefresh and just calculate it on demand. Saves
a bit of space and avoids the cached value getting out of sync
with reality.
Mostly done with cocci, with the following manual fixups:
- Remove the now empty loop in drm_helper_probe_single_connector_modes()
- Fix __MODE() macro in ch7006_mode.c
- Fix DRM_MODE_ARG()
2006 Jul 26
5
linux-2.6-xen.hg
Hi,
Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being
updated? if not, what''s the preferred Linux tree to track that has all
of the Xen bits?
Thanks,
Muli
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2006 Aug 30
30
Testing for the 4.4p1 release
Hi,
The 4.4p1 release is approaching now, so we are now asking people to
actively test snapshots or CVS and report back to the mailing list.
Snapshots are available from http://www.mindrot.org/openssh_snap or
from any of the mirrors listed on http://www.openssh.org/portable.html
The latter page also includes instructions for checking out portable
OpenSSH via anonymous CVS.
This release