On Sun, Nov 25, 2012 at 12:17:03AM -0800, Jonathan Nieder wrote:
> Unfortunately 99f5944b8477 fixes a regression introduced in
> v3.5-rc3~1^2~14 (Btrfs: use rcu to protect device->name, 2012-06-04),
> so it can't be the fix on its own. How did you track down that patch?
> E.g., did you bisect?
No
tags 687456 + moreinfo
quit
Hi Antoine,
Antoine Sirinelli wrote:
> This bug has been fixed by this commit
>
> commit 99f5944b8477914406173b47b4f261356286730b
> Btrfs: do not strdup non existent strings
Sorry for the slow response.
Unfortunately 99f5944b8477 fixes a regression introduced in
tags 687456 patch
thanks
This bug has been fixed by this commit
commit 99f5944b8477914406173b47b4f261356286730b
Btrfs: do not strdup non existent strings
This is available in 3.6.0-rc5.
Can this patch be cherry-picked?
Antoine
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.d
severity 687456 normal
thanks
In fact I created the RAID1-like filesystem the wrong way (btrfs wiki
is wrong). I was using a RAID1 strategy only for the metadata and not
the data. With the following command-line to create the fs, I no longer
get the Oops:
# mkfs.btrfs -m raid1 -d raid1 /dev/vdb /
Package: src:linux
Version: 3.2.23-1
Severity: grave
On a very fresh wheezy install I was able to crash the kernel by
playing with btrfs. I am reporting it using a kvm image but I first
had the bug on real boxes.
To reproduce the bug, I am creating a "raid1" btrfs filesystem,
creating some file a
5 matches
Mail list logo
