Bug#1039883: [PATCH] ext4: don't track ranges in fast_commit if inode has inlined data

On Wed 19 Jun 2024 12:30:38 AM +02, Ben Hutchings wrote; > On Tue, 2024-06-18 at 15:43 +0100, Luis Henriques (SUSE) wrote: >> When fast-commit needs to track ranges, it has to handle inodes that have >> inlined data in a different way because ext4_fc_write_inode_data(), in the &

Bug#1039883: [PATCH] ext4: don't track ranges in fast_commit if inode has inlined data

inode->i_block and, eventually, in the extended attribute space. Unfortunately, because fast commit doesn't currently support extended attributes, the solution is to mark this commit as ineligible. Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039883 Signed-off-by: Luis He

Bug#1039883: linux: ext4 corruption with symlinks

On Tue 18 Jun 2024 10:52:55 AM +01, Luis Henriques wrote; > On Fri 14 Jun 2024 05:18:45 PM +01, Luis Henriques wrote; > [...} >>> >>> I can also reproduce this error message using the above script and: >>> >>> - Linux 6.10-rc2 >>> - A 2 GiB lo

Bug#1039883: linux: ext4 corruption with symlinks

On Fri 14 Jun 2024 05:18:45 PM +01, Luis Henriques wrote; [...} >> >> I can also reproduce this error message using the above script and: >> >> - Linux 6.10-rc2 >> - A 2 GiB loopback devic instead of /dev/sdb >> >> I bisected this back to: >> &g

Bug#1039883: linux: ext4 corruption with symlinks

On Mon 10 Jun 2024 06:03:58 PM +02, Ben Hutchings wrote; > On Sun, 5 Nov 2023 16:12:41 + Hervé Werner > wrote: >> Hello >> >> I'm sorry for the delay. >> >> > Are you able to reliably preoeduce the issue and can bisect it to >> > the introducing commit? >> I faced this issue on real data bu

Bug#802885: [3.16] xfs: allow inode allocations in post-growfs disk space

On Mon, Dec 14, 2015 at 11:42:26AM +1100, Dave Chinner wrote: > On Sun, Dec 13, 2015 at 12:27:39AM +, Ben Hutchings wrote: > > Per the FAQ at > > , > > I think the following commit should be cherry

Bug#797023: Linux kernel FTBFS error for ARCH=s390, CONFIG_SMP=n, and CONFIG_DYNAMIC_DEBUG=y

On Mon, Aug 31, 2015 at 06:47:01PM -0400, Stephen Powell wrote: > > On Thu, 27 Aug 2015 18:06:49 -0400 (EDT), Ben Hutchings wrote: > > > > On Wed, 2015-08-26 at 21:33 -0400, Stephen Powell wrote: > >> > >> The Linux kernel in jessie fails to build from source for > >> the combination ARCH=s390,

Bug#782515: [PATCH stable 3.10-3.16] tcp: Fix crash in TCP Fast Open

On Wed, Apr 15, 2015 at 07:00:32PM +0100, Ben Hutchings wrote: > Commit 355a901e6cf1 ("tcp: make connect() mem charging friendly") > changed tcp_send_syn_data() to perform an open-coded copy of the 'syn' > skb rather than using skb_copy_expand(). > > The open-coded copy does not cover the skb_shar

Bug#769576: linux: Btrfs goes forced readonly when qgroup already exists

Hi Sebastiann, On Mon, Jan 05, 2015 at 12:01:06AM +, Andy Whitcroft wrote: > On Sun, Jan 04, 2015 at 07:05:24PM +0100, Sebastiaan L. Zoutendijk wrote: > > Control: submitter -1 ! > > > > Hello Joe, > > > > On Sat 3 Jan 2015 at 16:02:12 -0500, Joseph Salisbury wrote: > > > Would it be possib

Re: [Precise][CVE-2014-9090] x86_64, traps: Stop using IST for #SS

On Sun, Dec 07, 2014 at 09:43:33PM +, Ben Hutchings wrote: > I think you want these too: > > af726f21ed8a x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C > b645af2d5905 x86_64, traps: Rework bad_iret > > I'm attaching backports to 3.2. > Thanks Ben. Initially Andy asked to wa

Re: [CVE-2014-9090] x86_64, traps: Stop using IST for #SS

On Sat, Dec 06, 2014 at 06:13:08PM +0100, Willy Tarreau wrote: > Hi Luis, > > On Fri, Dec 05, 2014 at 03:21:01PM +0000, Luis Henriques wrote: > > Your backport of commit 6f442be2fb22 ("x86_64, traps: Stop using IST > > for #SS") seems to be identical to mine, but I&

Re: [CVE-2014-9090] x86_64, traps: Stop using IST for #SS

Hi Willy, On Fri, Dec 05, 2014 at 02:57:26PM +0100, Willy Tarreau wrote: > Hi Luis, > > On Fri, Dec 05, 2014 at 01:51:45PM +0000, Luis Henriques wrote: > > [ Re-sending as I missed some people on the CC list. Sorry! ] > > > > Following this email I am sending for r

[Precise][CVE-2014-9090] x86_64, traps: Stop using IST for #SS

Andy Lutomirski Reviewed-by: Thomas Gleixner Cc: sta...@vger.kernel.org Signed-off-by: Linus Torvalds (backported from commit 6f442be2fb22be02cafa606f1769fa1e6f894441) CVE-2014-9090 BugLink: http://bugs.launchpad.net/bugs/1398795 Signed-off-by: Luis Henriques --- arch/x86/include/asm/page_32_types.h

[Lucid][CVE-2014-9090] x86_64, traps: Stop using IST for #SS

Andy Lutomirski Reviewed-by: Thomas Gleixner Cc: sta...@vger.kernel.org Signed-off-by: Linus Torvalds (backported from commit 6f442be2fb22be02cafa606f1769fa1e6f894441) CVE-2014-9090 BugLink: http://bugs.launchpad.net/bugs/1398795 Signed-off-by: Luis Henriques --- arch/x86/include/asm/page_32_types.h

[CVE-2014-9090] x86_64, traps: Stop using IST for #SS

[ Re-sending as I missed some people on the CC list. Sorry! ] Following this email I am sending for review the CVE-2014-9090 fix backports for both Lucid (2.6.32) and Precise (3.2.0). I'm also CC'ing Debian mailing-lists, Moritz, Ben and Willy as these backports could be of interest both to Debi

[Precise][CVE-2014-9090] x86_64, traps: Stop using IST for #SS

Andy Lutomirski Reviewed-by: Thomas Gleixner Cc: sta...@vger.kernel.org Signed-off-by: Linus Torvalds (backported from commit 6f442be2fb22be02cafa606f1769fa1e6f894441) CVE-2014-9090 BugLink: http://bugs.launchpad.net/bugs/1398795 Signed-off-by: Luis Henriques --- arch/x86/include/asm/page_32_types.h

[CVE-2014-9090] x86_64, traps: Stop using IST for #SS

Following this email I am sending for review the CVE-2014-9090 fix backports for both Lucid (2.6.32) and Precise (3.2.0). I'm also CC'ing Debian mailing-lists, Moritz, Ben and Willy as these backports could be of interest both to Debian and to the 2.6.32 and 3.2 stable kernels. Andy Lutomirski (1

[Lucid][CVE-2014-9090] x86_64, traps: Stop using IST for #SS

Andy Lutomirski Reviewed-by: Thomas Gleixner Cc: sta...@vger.kernel.org Signed-off-by: Linus Torvalds (backported from commit 6f442be2fb22be02cafa606f1769fa1e6f894441) CVE-2014-9090 BugLink: http://bugs.launchpad.net/bugs/1398795 Signed-off-by: Luis Henriques --- arch/x86/include/asm/page_32_types.h

Re: [ANNOUNCE] Linux 3.16.y.z extended stable support

On Thu, Oct 30, 2014 at 06:17:01PM +, Luis Henriques wrote: > The Ubuntu kernel team is pleased to announce that we will be > providing extended stable support for the Linux 3.16 kernel until > April 2016 as a third party effort maintained on our infrastructure. > The team will pi

[ANNOUNCE] Linux 3.16.y.z extended stable support

The Ubuntu kernel team is pleased to announce that we will be providing extended stable support for the Linux 3.16 kernel until April 2016 as a third party effort maintained on our infrastructure. The team will pick up stable maintenance where Greg KH left off with v3.16.7 [1]. Thank you, Greg. I

Re: Kernel version for jessie

On Sun, Jul 20, 2014 at 11:39:15PM +0100, Ben Hutchings wrote: > On Fri, 2014-07-18 at 17:43 +0100, Ben Hutchings wrote: > [...] > > Linux 3.16-stable > > - Supported by Ubuntu kernel team for about 15-18 months after distro > > release (October 2014) > [...] > > Note, that period is based on it

Bug#751417: linux-image-3.2.0-4-5kc-malta: no SIGKILL after prctl(PR_SET_SECCOMP, 1, ...) on MIPS

On Thu, Jun 12, 2014 at 09:21:41PM +0100, Ben Hutchings wrote: > On Thu, 2014-06-12 at 20:36 +0100, Ben Hutchings wrote: > > Control: tag -1 security upstream patch moreinfo > > Control: severity -1 grave > > Control: found -1 3.14.5-1 > > Aurelien Jarno pointed out this appears to be fixed upstre

Bug#648155: [stable] SUNRPC handle EKEYEXPIRED in call_refreshresult

On Thu, Nov 21, 2013 at 04:16:48AM +, Ben Hutchings wrote: > On Tue, 2013-11-05 at 21:20 +0100, Bastian Blank wrote: > > On Tue, Nov 05, 2013 at 05:36:12PM +0100, Per Olofsson wrote: > > > Seems that maybe they reverted to the old behavior after all: > > > https://git.kernel.org/cgit/linux/kern

Bug#714295: [PATCH libata/for-3.11-fixes] libata: make it clear that sata_inic162x is experimental

Tejun Heo writes: > Hello, Greg. > > I think the following commit should go into -stable but forgot to cc > stable. It's now in Linus' tree. Can you please include it in > -stable? > > Thanks! > > On Mon, Jul 22, 2013 at 05:13:07PM -0400, Tejun Heo wrote: >> From bb9696192826a7d9279caf872e95b41

Bug#709647: [PATCH 14/98] genirq: Fix can_request_irq() for IRQs without an action

jarni Ingi Gislason Tested-by: Bjarni Ingi Gislason (against 3.2) Signed-off-by: Ben Hutchings Cc: 709...@bugs.debian.org Link: http://bugs.debian.org/709647 Link: http://lkml.kernel.org/r/1372383630.23847.40.ca...@deadeye.wl.decadent.org.uk Signed-off-by: Thomas Gleixner Signed-off-by: Luis

Bug#709647: [ 3.8.y.z extended stable ] Patch "genirq: Fix can_request_irq() for IRQs without an action" has been added to staging queue

Reported-by: Bjarni Ingi Gislason Tested-by: Bjarni Ingi Gislason (against 3.2) Signed-off-by: Ben Hutchings Cc: 709...@bugs.debian.org Link: http://bugs.debian.org/709647 Link: http://lkml.kernel.org/r/1372383630.23847.40.ca...@deadeye.wl.decadent.org.uk Signed-off-by: Thomas Gleixner Signed

Bug#709647: [ 3.5.y.z extended stable ] Patch "genirq: Fix can_request_irq() for IRQs without an action" has been added to staging queue

Reported-by: Bjarni Ingi Gislason Tested-by: Bjarni Ingi Gislason (against 3.2) Signed-off-by: Ben Hutchings Cc: 709...@bugs.debian.org Link: http://bugs.debian.org/709647 Link: http://lkml.kernel.org/r/1372383630.23847.40.ca...@deadeye.wl.decadent.org.uk Signed-off-by: Thomas Gleixner Signed

Bug#700333: [PATCH 102/118] clockevents: Set dummy handler on CPU_DEAD shutdown

handler_noop) which forgot to fix it up in tick_shutdown(). Same issue with the broadcast device. Reported-by: Vitaliy Fillipov Cc: Ben Hutchings Cc: 700...@bugs.debian.org Signed-off-by: Thomas Gleixner [ luis: adjust context ] Signed-off-by: Luis Henriques --- kernel/time/tick-broadcast.c | 4

Bug#700333: [ 3.5.y.z extended stable ] Patch "clockevents: Set dummy handler on CPU_DEAD shutdown" has been added to staging queue

ing up handler_noop) which forgot to fix it up in tick_shutdown(). Same issue with the broadcast device. Reported-by: Vitaliy Fillipov Cc: Ben Hutchings Cc: 700...@bugs.debian.org Signed-off-by: Thomas Gleixner [ luis: adjust context ] Signed-off-by: Luis Henriques --- kernel/time/tick-broadcas

Bug#704933: [stable] fbcon: fix locking harder

On Mon, Apr 22, 2013 at 02:26:07AM +0100, Ben Hutchings wrote: > On Mon, 2013-04-15 at 02:24 +0100, Ben Hutchings wrote: > > On Sat, 2013-04-13 at 03:28 +0400, Stepan Golosunov wrote: > > [...] > > > The relevant changes in 3.2.40 ( > > > fb: rework locking to fix lock ordering on takeover, > > > f

Bug#684441: [PATCH v2] [media] rc: ite-cir: Initialise ite_dev::rdev earlier

On Tue, Aug 28, 2012 at 10:09:55AM -0700, Ben Hutchings wrote: > On Tue, 2012-08-28 at 12:44 +0100, Luis Henriques wrote: > > On Mon, Aug 20, 2012 at 12:32:27AM +0100, Ben Hutchings wrote: > > > ite_dev::rdev is currently initialised in ite_probe() after > > > rc_regis

Bug#684441: [PATCH v2] [media] rc: ite-cir: Initialise ite_dev::rdev earlier

On Mon, Aug 20, 2012 at 12:32:27AM +0100, Ben Hutchings wrote: > ite_dev::rdev is currently initialised in ite_probe() after > rc_register_device() returns. If a newly registered device is opened > quickly enough, we may enable interrupts and try to use ite_dev::rdev > before it has been initialis

Re: Kernel built with CONFIG_PREEMPT_RT

Ben Hutchings writes: > On Tue, 2011-07-12 at 11:25 +0100, Luis Henriques wrote: >> Hi, >> >> (why do you keep replying only to the sender?) >> >> Lars Segerlund writes: > [...] >> > I think CONFIG_PREEMPT_VOLUNTARy is a good choise for the de

Re: Kernel built with CONFIG_PREEMPT_RT

ld all the > time ... What's wrong with rebuilding the kernel? $ uname -r 3.0.0-rc7 :-) Cheers, -- Luis Henriques -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87fwmbaj9c@gmail.com

Re: Kernel built with CONFIG_PREEMPT_RT

IG_PREEMPT, right? At least my 2.6.39-2 is already using CONFIG_SMP and CONFIG_IRQ_FORCED_THREADING by default. Not sure about the rational behind picking CONFIG_PREEMPT_VOLUNTARY instead of CONFIG_PREEMPT, but I would say that it could make sense to at least evaluate the possibility to change this. Chee

Re: Kernel built with CONFIG_PREEMPT_RT

t "official" version of this patch is 2.6.33.9-rt31, so there is no support for latter kernels. Cheers, -- Luis Henriques -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ipr9t3nj@gmail.com

Re: r8169 update for Debian 6.0 'squeeze'

sed fatal: unable to connect a socket (Connection refused) Anyway, I am currently running wheezy, but since my laptop is using this driver, I believe it shouldn't hurt to give it a try. Any suggestions on what sort of tests I could run? Or just reporting "it's working f