February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 824171] prepared kernel update openSUSE_Maintenance_1695 is not installable
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

1 0

[Bug 1010414] rst2html5 depends on Pygments 2.0.2 while Pygments 2.1.3 are available
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1010414 http://bugzilla.opensuse.org/show_bug.cgi?id=1010414#c4 Carmen Bianca Bakker <c.b.bakker(a)carmenbianca.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #4 from Carmen Bianca Bakker <c.b.bakker(a)carmenbianca.eu> --- Upstream has accepted my PR :) That was quick. The patch should be a stopgap solution until a new version is released. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1024165] New: btrfs: skip waiting on ordered range for special files
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024165 Bug ID: 1024165 Summary: btrfs: skip waiting on ordered range for special files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From jeffm(a)suse.com Tue Feb 7 18:02:34 2017 From: Jeff Mahoney <jeffm(a)suse.com> Subject: btrfs: skip waiting on ordered range for special files References: bko#100911 In btrfs_evict_inode, we properly truncate the page cache for evicted inodes but then we call btrfs_wait_ordered_range for every inode as well. It's the right thing to do for regular files but results in incorrect behavior for device inodes for block devices. filemap_fdatawrite_range gets called with inode->i_mapping which gets resolved to the block device inode before getting passed to wbc_attach_fdatawrite_inode and ultimately to inode_to_bdi. What happens next depends on whether there's an open file handle associated with the inode. If there is, we write to the block device, which is unexpected behavior. If there isn't, we through normally and inode->i_data is used. We can also end up racing against open/close which can result in crashes when i_mapping points to a block device inode that has been closed. Since there can't be any page cache associated with special file inodes, it's safe to skip the btrfs_wait_ordered_range call entirely and avoid the problem. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=100911 Signed-off-by: Jeff Mahoney <jeffm(a)suse.com> --- fs/btrfs/inode.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1024114] VUL-0: kvm: qemu: virtio: integer overflow in handling virtio-crypto requests
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024114 http://bugzilla.suse.com/show_bug.cgi?id=1024114#c1 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium --- Comment #1 from Swamp Workflow Management <swamp(a)suse.de> --- bugbot adjusting priority -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1024164] New: btrfs: skip waiting on ordered range for special files
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024164 Bug ID: 1024164 Summary: btrfs: skip waiting on ordered range for special files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- From: Jeff Mahoney <jeffm(a)suse.com> Subject: btrfs: skip waiting on ordered range for special files References: bko#100911 In btrfs_evict_inode, we properly truncate the page cache for evicted inodes but then we call btrfs_wait_ordered_range for every inode as well. It's the right thing to do for regular files but results in incorrect behavior for device inodes for block devices. filemap_fdatawrite_range gets called with inode->i_mapping which gets resolved to the block device inode before getting passed to wbc_attach_fdatawrite_inode and ultimately to inode_to_bdi. What happens next depends on whether there's an open file handle associated with the inode. If there is, we write to the block device, which is unexpected behavior. If there isn't, we through normally and inode->i_data is used. We can also end up racing against open/close which can result in crashes when i_mapping points to a block device inode that has been closed. Since there can't be any page cache associated with special file inodes, it's safe to skip the btrfs_wait_ordered_range call entirely and avoid the problem. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=100911 Signed-off-by: Jeff Mahoney <jeffm(a)suse.com> --- fs/btrfs/inode.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1024161] New: This is a test bug
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024161 Bug ID: 1024161 Summary: This is a test bug Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a test bug description. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1024160] New: This is a test bug
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024160 Bug ID: 1024160 Summary: This is a test bug Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a test bug description. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1024158] New: This is a test bug
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024158 Bug ID: 1024158 Summary: This is a test bug Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- TThis is a test bug using the python script. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1024138] New: Btrfs: fix warning of bytes_may_use
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024138 Bug ID: 1024138 Summary: Btrfs: fix warning of bytes_may_use Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- From: Liu Bo <bo.li.liu(a)oracle.com> Date: Wed, 17 Jun 2015 16:59:58 +0800 Subject: Btrfs: fix warning of bytes_may_use Git-commit: ddba1bfc2369cd0566bcfdab47599834a32d1c19 Patch-mainline: v4.2-rc2 References: revisit While running generic/019, dmesg got several warnings from btrfs_free_reserved_data_space(). Test generic/019 produces some disk failures so sumbit dio will get errors, in which case, btrfs_direct_IO() goes to the error handling and free bytes_may_use, but the problem is that bytes_may_use has been free'd during get_block(). This adds a runtime flag to show if we've gone through get_block(), if so, don't do the cleanup work. Signed-off-by: Liu Bo <bo.li.liu(a)oracle.com> Reviewed-by: Filipe Manana <fdmanana(a)suse.com> Tested-by: Filipe Manana <fdmanana(a)suse.com> Signed-off-by: Chris Mason <clm(a)fb.com> Acked-by: Jeff Mahoney <jeffm(a)suse.com> --- fs/btrfs/btrfs_inode.h | 2 ++ fs/btrfs/inode.c | 16 +++++++++++++--- 2 files changed, 15 insertions(+), 3 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1024154] New: Btrfs: fix warning of bytes_may_use
by bugzilla_noreply＠novell.com 07 Feb '17

07 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1024154 Bug ID: 1024154 Summary: Btrfs: fix warning of bytes_may_use Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Btrfs: fix warning of bytes_may_use -- You are receiving this mail because: You are on the CC list for the bug.

1 2