On 11/27/2015 12:07 PM, Filipe Manana wrote:
> Try the following (also pasted at
> https://friendpaste.com/5O6o1cqWqJZDIKrH1YqG7y):
Doesn't apply neither against the used 4.2.6 kernel nor aginst current git HEAD
:
t44 linux # patch -p1 --dry-run <
On 11/27/2015 12:53 PM, Filipe Manana wrote:
> Indeed.
> Try the following instead: http://paste.opensuse.org/view/raw/58412382
white-space damaged too, but the hint with --ingore- made it.
Will see, if it helps now. But FWIW the mentioned spew happened the first time
here AFAICT.
--
Toralf,
Happened today few times in a row at a stable 64 bit Gentoo hardened system:
Nov 27 10:23:09 t44 kernel: [41619.519921] PAX: size overflow detected in
function try_merge_map fs/btrfs/extent_map.c:238 cicus.107_102 max, count: 13,
decl: block_len; num: 0; context: extent_map;
Nov 27 10:23:09
On 05/13/2015 07:46 PM, Calvin Walton wrote:
On Wed, 2015-05-13 at 16:13 +0200, Toralf Förster wrote:
To support the Gentoo Linux ecosystem I do maintain a server as a
tinderbox. I create chroot images based on various Gentoo minmal ISO
images. I usually run 4 chroot image jobs in parallel
Within a 32 bit KVM (stable Gentoo) I run into this situation using trinity
(latest git):
tfoerste@n22kvm-clone ~ $ D=/mnt/ramdisk/btrfs; while [[ : ]]; do cd ~; sudo rm
-rf $D/t3 mkdir $D/t3 || break; cd $D/t3; mkdir -p v1/v2; for i in $(seq 0
99); do touch v1/v2/f$i; mkdir v1/v2/d$i; done;
I do run latest trinity at a 32 bit x86 KVM guest with guest kernel 4.0.ß0-rc5
(host is a 64 bit hardened Gentoo FWIW). Within KVM I prepared a victim file
system via :
$ mkdir /mnt/ramdisk/btrfs; truncate -s 497M /mnt/ramdisk/btrfs.fs;
/sbin/mkfs.btrfs /mnt/ramdisk/btrfs.fs; sudo su -c mount
Just like to share this :
CC fs/btrfs/print-tree.o
fs/btrfs/extent-tree.c: In function ‘find_free_extent’:
fs/btrfs/extent-tree.c:6402:34: warning: ‘used_bg’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
struct btrfs_block_group_cache *used_bg;
At a 32 bit Gentoo Linux I get with 3.18.5 the following syslog message:
Feb 4 22:09:36 n22 kernel: INFO: trying to register non-static key.
Feb 4 22:09:36 n22 kernel: the code is fine but needs lockdep annotation.
Feb 4 22:09:36 n22 kernel: turning off the locking correctness validator.
Feb
I created within a x86 KVM guest at a tmpfs file system under 3.19.0-rc1 a 257
MB file, created within that abtrfs file system and run the fuzzer trinity
using that fs for its victim files:
$ mkdir /mnt/ramdisk/btrfs; truncate -s 257M /mnt/ramdisk/btrfs.fs;
/sbin/mkfs.btrfs
I'm unsure if I already reported this particular issue in detail or not :
As soon as I do start a fuzz testing BTRFS at a 32 bit qemu KVM amachine using
the follwoing commands:
$ mkdir /mnt/ramdisk/btrfs; truncate -s 97M /mnt/ramdisk/btrfs.fs;
/sbin/mkfs.btrfs /mnt/ramdisk/btrfs.fs; sudo su -c
On 10/31/2014 02:36 AM, Liu Bo wrote:
On Fri, Oct 31, 2014 at 12:33:43AM +0100, Toralf Förster wrote:
On 10/30/2014 11:15 AM, Liu Bo wrote:
On Wed, Oct 29, 2014 at 05:56:33PM +0100, Toralf Förster wrote:
This is new in my eyes, or ? :
Also new to me, could you please turn on lock debug
On 10/31/2014 03:12 PM, Liu Bo wrote:
Can you please tell me the trinity option?
(I'm using trinity --dangerous -C 2 -N 200 -c writev -q -l off, But I only
got softlockup for one time, others are OOM messages.)
thanks,
-liubo
I'm running within the 32 bit KVM guest :
$ mkdir
On 10/30/2014 11:15 AM, Liu Bo wrote:
On Wed, Oct 29, 2014 at 05:56:33PM +0100, Toralf Förster wrote:
This is new in my eyes, or ? :
Also new to me, could you please turn on lock debug and try again?
thanks,
-liubo
you mean CONFIG_PROVE_LOCKING=y right ?
--
Toralf
pgp key: 0076 E94E
This is new in my eyes, or ? :
Oct 29 17:53:04 n22kvmclone kernel: INFO: trying to register non-static key.
Oct 29 17:53:04 n22kvmclone kernel: the code is fine but needs lockdep
annotation.
Oct 29 17:53:04 n22kvmclone kernel: turning off the locking correctness
validator.
Oct 29 17:53:04
On 09/01/2014 03:41 PM, Liu Bo wrote:
I believe that this warning of btrfs_evict_inode also comes from a result of
lseek, and Chris said that he's prepared a fix for that, so it's queued in the
next version.
thanks,
-liubo
So rather fixed in -rc6 because v3.17-rc4-337-gfc486b0 still
At a 32 bit stable Gentoo Linux I do have 2 BTRFS file systems :
$ mount | grep btrfs
/var/lib/portage.fs on /usr/portage type btrfs (rw,noatime,compress=lzo)
/var/lib/pkg.fs on /var/db/pkg type btrfs (rw,noatime,compress=lzo)
holding a lot of small Gentoo-package-Manager-related files. The
On 09/01/2014 03:41 PM, Liu Bo wrote:
I believe that this warning of btrfs_evict_inode also comes from a result of
lseek, and Chris said that he's prepared a fix for that, so it's queued in the
next version.
thanks,
-liubo
Ah thx, it seems that fix does not made it in -rc3, so -rc4 would
At as 32 bit KVM I run these 2 commands:
tfoerste@n22kvm ~ $ mkdir /mnt/ramdisk/btrfs; truncate -s 97M
/mnt/ramdisk/btrfs.fs; /sbin/mkfs.btrfs /mnt/ramdisk/btrfs.fs; sudo su -c
mount -o loop,compress=lzo /mnt/ramdisk/btrfs.fs /mnt/ramdisk/btrfs; chmod 777
/mnt/ramdisk/btrfs
tfoerste@n22kvm ~
Hello,
a recent kernel brought up this while using trinity inside a x86 UML (stable
Gentoo Linux):
Aug 14 22:07:06 trinity kernel: [ cut here ]
Aug 14 22:07:06 trinity kernel: WARNING: CPU: 0 PID: 5860 at
fs/btrfs/extent_io.c:430 insert_state+0x69/0x170()
Aug 14
/me wonders if this
if (ret = 0) {
/* Add an item for the type for the first time */
eb = path-nodes[0];
slot = path-slots[0];
offset = btrfs_item_ptr_offset(eb, slot);
} else if (ret == -EEXIST) {
/*
in new_thread_handler () at arch/um/kernel/process.c:129
Well, this might be just an expected behaviour of the used fuzzing tool, but
from my experiences with fuzz testings in the past (with NFSv4) this might
indicate a BTRFS issue instead.
- --
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F
/loop1
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/2013 12:04 PM, Hugo Mills wrote:
At a guess, two of those are probably from btrfs dev scan
triggered by udev.
Those messages do only appear for a btrfs, not if I choose ext4.
- --
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4
kernel: btrfs: disk space caching is enabled
2013-05-09T14:43:35.660+02:00 n22 kernel: device fsid
20a30a6b-a82f-429f-b426-00f1739e4d3d devid 1 transid 8 /dev/loop1
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list
24 matches
Mail list logo
