On Wed, Mar 17, 2021 at 10:51:51AM +0100, David Sterba wrote:
> From: Qu Wenruo
>
> [ Upstream commit b12de52896c0e8213f70e3a168fde9e6eee95909 ]
>
> [BUG]
> When running btrfs/072 with only one online CPU, it has a pretty high
> chance to fail:
>
> btrfs/072 12s ... _check_dmesg: something fo
On Tue, Feb 16, 2021 at 06:52:21PM +0100, David Sterba wrote:
> On Tue, Feb 16, 2021 at 04:34:27PM +0100, Greg KH wrote:
> > On Tue, Feb 16, 2021 at 04:15:46PM +0100, David Sterba wrote:
> > > On Tue, Feb 16, 2021 at 03:50:36PM +0100, Greg KH wrote:
> > > > On Tue, Fe
On Tue, Feb 16, 2021 at 04:15:46PM +0100, David Sterba wrote:
> On Tue, Feb 16, 2021 at 03:50:36PM +0100, Greg KH wrote:
> > On Tue, Feb 16, 2021 at 02:40:31PM +, fdman...@kernel.org wrote:
> > > From: Filipe Manana
> > >
> > > Whenever we attempt to d
On Tue, Feb 16, 2021 at 02:40:31PM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> Whenever we attempt to do a non-aligned direct IO write with O_DSYNC, we
> end up triggering an assertion and crashing. Example reproducer:
>
> $ cat test.sh
> #!/bin/bash
>
> DEV=/dev/sdj
> M
On Mon, Feb 15, 2021 at 02:35:35PM +, Michal Rostecki wrote:
> On Sat, Feb 13, 2021 at 11:19:28AM +0100, Greg KH wrote:
> > On Tue, Feb 09, 2021 at 09:30:39PM +0100, Michal Rostecki wrote:
> > > From: Michal Rostecki
> > >
> > > Before this change, ra
On Tue, Feb 09, 2021 at 09:30:39PM +0100, Michal Rostecki wrote:
> From: Michal Rostecki
>
> Before this change, raid1 read policy could be selected by using the
> /sys/fs/btrfs/[fsid]/read_policy file.
>
> Change it to /sys/fs/btrfs/[fsid]/read_policies/policy.
>
> The motivation behing creati
On Mon, Sep 16, 2019 at 01:59:47PM +0100, Filipe Manana wrote:
> On Thu, Sep 12, 2019 at 8:32 AM Sasha Levin wrote:
> >
> > Hi,
> >
> > [This is an automated email]
> >
> > This commit has been processed because it contains a -stable tag.
> > The stable tag indicates that it's relevant for the fol
On Mon, Sep 16, 2019 at 10:17:24AM +0200, Johannes Thumshirn wrote:
> Hi Greg,
>
> Here's the backport of aa53e3bfac72 ("btrfs: correctly validate compression
> type") for v4.14 with it's prerequisite e128f9c3f724 ("btrfs: compression:
> add helper for type to string conversion").
>
> David Sterb
On Fri, Sep 13, 2019 at 01:55:08PM +0200, Johannes Thumshirn wrote:
> On 13/09/2019 13:53, Greg KH wrote:
> [...]
> > We also need this for 4.14.y, let me see if it is easy to backport...
>
> Haven't had a look at it. If you need help just ping me (or tell me
> right awa
On Thu, Sep 12, 2019 at 06:52:15AM -0400, Sasha Levin wrote:
> On Thu, Sep 12, 2019 at 12:02:59PM +0200, Johannes Thumshirn wrote:
> > [ Upstream commit aa53e3bfac7205fb3a8815ac1c937fd6ed01b41e ]
> >
> > Nikolay reported the following KASAN splat when running btrfs/048:
> >
> > [ 1843.470920]
>
On Wed, Aug 07, 2019 at 11:47:59AM +0200, David Sterba wrote:
> On Tue, Aug 06, 2019 at 05:35:00PM -0400, Sasha Levin wrote:
> > From: Filipe Manana
> >
> > [ Upstream commit a6d155d2e363f26290ffd50591169cb96c2a609e ]
> >
> > Fixes: 03628cdbc64db6 ("Btrfs: do not start a transaction during fiema
On Mon, Jul 08, 2019 at 02:01:34PM +0200, Stanislaw Gruszka wrote:
> Upstream commit 38e3eebff643 ("btrfs: honor path->skip_locking in
> backref code") was incorrectly backported to 4.14.y . It misses removal
> of two lines from original commit, what cause deadlock.
>
> Bugzilla: https://bugzilla.
On Wed, Jul 03, 2019 at 12:45:49PM +0300, Nikolay Borisov wrote:
> Recent FITRIM work, namely bbbf7243d62d ("btrfs: combine device update
> operations during transaction commit") combined the way certain
> operations are recoded in a transaction. As a result an ASSERT was added
> in dev_replace_fin
On Tue, May 28, 2019 at 06:23:53PM +0800, Qu Wenruo wrote:
> From: Josef Bacik
>
> Commit 38e3eebff643db725633657d1d87a3be019d1018.
Thanks for the backports, now queued up.
greg k-h
On Thu, Apr 05, 2018 at 07:11:14PM +0200, David Sterba wrote:
> On Thu, Apr 05, 2018 at 04:42:34PM +, Sasha Levin wrote:
> > Hi.
> >
> > [This is an automated email]
> >
> > This commit has been processed by the -stable helper bot and determined
> > to be a high probability candidate for -sta
On Tue, Apr 03, 2018 at 11:57:26AM -0700, Linus Torvalds wrote:
>
> Greg - if your automation has changed, and you actually really want
> the "vger", let me know. Because I tend to just use
> "sta...@kernel.org"
Either is fine, my scripts pick up both variants.
thanks,
greg k-h
--
To unsubscrib
On Fri, Feb 16, 2018 at 07:51:38PM +, Dmitriy Gorokh wrote:
> On detaching of a disk which is a part of a RAID6 filesystem, the following
> kernel OOPS may happen:
>
> [63122.680461] BTRFS error (device sdo): bdev /dev/sdo errs: wr 0, rd 0,
> flush 1, corrupt 0, gen 0
> [63122.719584] BTRFS
On Fri, Aug 04, 2017 at 11:25:14PM +0300, Nikolay Borisov wrote:
> Hello,
>
> I'd like to aforementioned patch to be applied to stable 4.9/4.12. The
> attached backport applies cleanly to both of them.
Thanks, I'll queue it up after this next release happens.
greg k-h
--
To unsubscribe from this
On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
> On 02/02/2017 01:23 PM, Greg KH wrote:
> > On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> >> Hello,
> >>
> >> Please consider reverting commit
> >> 4c63c2454eff99
On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> Hello,
>
> Please consider reverting commit
> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
What release can I remove it from?
It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
reverted in
On Tue, Aug 16, 2016 at 11:18:52AM -0700, Deepa Dinamani wrote:
> Thank you for the suggestion.
>
> > Who are you execting to pull this huge patch series?
>
> The last pull request was addressed to Al as per Arnd's suggestion.
> I'm not completely sure who should it be addressed to.
>
> > Why no
On Sat, Aug 13, 2016 at 03:48:12PM -0700, Deepa Dinamani wrote:
> The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC
> macros.
> The macros are not y2038 safe. There is no plan to transition them into being
> y2038 safe.
> ktime_get_* api's can be used in their place. And, the
On Wed, Dec 09, 2015 at 11:29:48PM +, Filipe Manana wrote:
> On Wed, Dec 9, 2015 at 11:05 PM, Gerald Hopf
> wrote:
> >
> >>> kernel BUG at fs/btrfs/extent-tree.c:1833!
> >>
> >> We got this fixed in 4.4-rc1:
> >>
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit
On Thu, Jun 25, 2015 at 05:10:29PM +0200, David Sterba wrote:
> On Fri, Jun 19, 2015 at 01:31:31PM -0700, Greg KH wrote:
> > > 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+
> >
> > Does not build on 3.14+, sorry. Please provide a backported version if
> > you
On Thu, Jun 11, 2015 at 06:06:32PM +0200, David Sterba wrote:
> Hi,
>
> please queue the following patches to 4.0 stable. There are fixes for user
> visible bugs and one usability regression with RAID1 -> single conversion
> during balance.
>
> One of the patches does not apply cleanly to 4.0.5,
On Thu, Jun 11, 2015 at 06:06:32PM +0200, David Sterba wrote:
> Hi,
>
> please queue the following patches to 4.0 stable. There are fixes for user
> visible bugs and one usability regression with RAID1 -> single conversion
> during balance.
>
> One of the patches does not apply cleanly to 4.0.5,
On Thu, Apr 23, 2015 at 02:16:40PM -0400, Rich Freeman wrote:
> On Mon, Apr 13, 2015 at 12:58 PM, Greg KH wrote:
> > On Mon, Apr 13, 2015 at 07:28:38PM +0500, Roman Mamedov wrote:
> >> On Thu, 2 Apr 2015 10:17:47 -0400
> >> Chris Mason wrote:
> >>
> >&g
On Mon, Apr 13, 2015 at 07:28:38PM +0500, Roman Mamedov wrote:
> On Thu, 2 Apr 2015 10:17:47 -0400
> Chris Mason wrote:
>
> > Hi stable friends,
> >
> > Can you please backport this one to 3.19.y. It fixes a bug introduced
> > by:
> >
> > 381cf6587f8a8a8e981bc0c18859b51dc756, which was ta
On Thu, Feb 12, 2015 at 10:53:14AM +0100, David Sterba wrote:
> Adding Greg to CC.
>
> On Thu, Feb 12, 2015 at 07:03:37AM +0800, Anand Jain wrote:
> > drivers/cpufreq/cpufreq.c is already using this function. And now btrfs
> > needs it as well. export symbol kobject_move().
> >
> > Signed-off-by:
On Tue, Oct 21, 2014 at 03:19:09PM -0400, Chris Mason wrote:
>
>
> On Mon, Oct 20, 2014 at 6:12 PM, Greg KH wrote:
> >On Mon, Oct 20, 2014 at 01:22:22PM +0100, Filipe Manana wrote:
> >
> >> May I suggest porting the following commit to 3.14 too?
> >>
>
On Mon, Oct 20, 2014 at 01:22:22PM +0100, Filipe Manana wrote:
>
>
> On 10/20/2014 12:13 AM, Greg KH wrote:
> > On Sun, Oct 19, 2014 at 09:55:11PM +0200, Greg KH wrote:
> >> On Sun, Oct 19, 2014 at 06:01:16AM -0400, Chris Mason wrote:
> >>> Hi everyone,
>
On Sun, Oct 19, 2014 at 09:55:11PM +0200, Greg KH wrote:
> On Sun, Oct 19, 2014 at 06:01:16AM -0400, Chris Mason wrote:
> > Hi everyone,
> >
> > I've pulled out some of the btrfs commits from the merge window that
> > we'd like to see in stable. The f
On Sun, Oct 19, 2014 at 06:01:16AM -0400, Chris Mason wrote:
> Hi everyone,
>
> I've pulled out some of the btrfs commits from the merge window that
> we'd like to see in stable. The full list of sha's from Linus is below,
> you can see 4 of them are only needed on 3.17
>
> 2fad4e83e12591eb3bd21
On Thu, Sep 04, 2014 at 06:37:58PM +0200, David Sterba wrote:
> On Wed, Sep 03, 2014 at 02:32:09PM -0700, Greg KH wrote:
> > > 6f7ff6d7832c6be13e8c95598884dbc40ad69fb7
> > This doesn't apply to 3.10-stable :(
> >
> > > ce62003f690dff38d3164a6
On Wed, Sep 03, 2014 at 04:50:47PM -0400, Chris Mason wrote:
> Hi everyone,
>
> For 3.16, please pull these into stable, I've cherry picked and tested
> them here. For 3.15 and earlier there are a few conflicts, so I'll make
> a git tree with things to pull.
>
> 8d875f95da43c6a8f18f77869f2ef26e9
On Tue, Aug 19, 2014 at 01:10:45PM +0200, David Sterba wrote:
> Hi stable team,
>
> please add the following patches to stable trees.
>
> Patch #3 applies to all currently live stables, a 7 years old bug. I've
> briefly reviewed all 3 patches against 3.10/12/14/16 (ie. 3.4 skips #1
> and #2).
>
On Sat, Jun 21, 2014 at 12:48:27PM -0700, Greg KH wrote:
> On Sat, Jun 21, 2014 at 01:05:53PM +0100, Ben Hutchings wrote:
> > On Fri, 2014-06-20 at 14:21 -0400, Joseph Salisbury wrote:
> > [...]
> > > I looked at this some more. It seems like my v2 backport may be the
>
On Sat, Jun 21, 2014 at 01:05:53PM +0100, Ben Hutchings wrote:
> On Fri, 2014-06-20 at 14:21 -0400, Joseph Salisbury wrote:
> [...]
> > I looked at this some more. It seems like my v2 backport may be the
> > most suitable for the releases mentioned in the subject line, but I'd
> > like to get add
On Mon, Feb 03, 2014 at 01:18:40PM -0500, Chris Mason wrote:
> On Mon 03 Feb 2014 12:54:05 PM EST, David Sterba wrote:
> >On Thu, Jan 30, 2014 at 04:52:54PM -0500, Chris Mason wrote:
> >>Chris Mason (3) commits (+64/-32):
> >> Btrfs: setup inode location during btrfs_init_inode_locked (+9/-9)
>
On Wed, Dec 18, 2013 at 04:14:02PM +0100, David Sterba wrote:
> Hi,
>
> please queue the following patches to 3.12 stable. They fix a few
> crashes or lockups that were reported by users.
>
> The patch "stop using vfs_read in send" may seem big for stable, but without
> it
> the send/receive ioc
On Mon, Nov 25, 2013 at 05:51:16PM +0100, David Sterba wrote:
> On Fri, Sep 27, 2013 at 09:37:00AM -0400, Josef Bacik wrote:
> > A user reported a problem where they were getting csum errors when running a
> > balance and running systemd's journal. This is because systemd is awesome
> > and
> > f
On Mon, Oct 07, 2013 at 04:34:43PM -0400, Josef Bacik wrote:
> On Sat, Oct 05, 2013 at 04:52:18PM -0700, Greg KH wrote:
> > On Fri, Sep 20, 2013 at 09:53:02AM -0700, Greg KH wrote:
> > > On Fri, Sep 20, 2013 at 06:34:39PM +0200, David Sterba wrote:
> > > > Hi stable
On Fri, Sep 20, 2013 at 09:53:02AM -0700, Greg KH wrote:
> On Fri, Sep 20, 2013 at 06:34:39PM +0200, David Sterba wrote:
> > Hi stable team,
> >
> > please add the following commits to 3.11 tree, they fix user visible
> > problems,
> > were teste
On Wed, Oct 02, 2013 at 01:15:19AM +, Chris Mason wrote:
> Sorry,
>
> I misunderstood and thought you had already queued them. Both are fine with
> me.
Ok, no worries, I'll pick them up in the next few days and add them to
the next stable releases.
thanks,
greg k-h
--
To unsubscribe from
On Tue, Oct 01, 2013 at 07:03:44PM +0200, David Sterba wrote:
> Hi Greg,
>
> On Fri, Sep 20, 2013 at 09:53:02AM -0700, Greg KH wrote:
> > Thanks for this, I'll queue them up soon.
>
> 3.11.3 has been just released and the btrfs fixes are not there nor in
> the sta
On Fri, Sep 20, 2013 at 06:34:39PM +0200, David Sterba wrote:
> Hi stable team,
>
> please add the following commits to 3.11 tree, they fix user visible problems,
> were tested and are now present in 3.12-rc1.
>
> 3d05ca371200b3366530621abf73769024581b79
> b13a004528c3e5eb060a26eee795f5a0da7bfe9f
On Mon, May 06, 2013 at 07:40:18PM +0200, Gabriel de Perthuis wrote:
> The search ioctl skips items that are too large for a result buffer, but
> inline items of a certain size occuring before any search result is
> found would trigger an overflow and stop the search entirely.
>
> Bug: https://bug
On Thu, Nov 08, 2012 at 10:35:19PM +0100, Alexander Block wrote:
>
> Used wrong CC for stable list. Corrected now.
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
--
To unsub
On Tue, Oct 30, 2012 at 06:45:19AM +0800, Zhi Yong Wu wrote:
> On Tue, Oct 30, 2012 at 6:34 AM, Greg KH wrote:
> > On Tue, Oct 30, 2012 at 06:25:50AM +0800, Zhi Yong Wu wrote:
> >> On Tue, Oct 30, 2012 at 2:11 AM, Greg KH
> >> wrote:
> >> > On Mon, Oc
On Tue, Oct 30, 2012 at 06:25:50AM +0800, Zhi Yong Wu wrote:
> On Tue, Oct 30, 2012 at 2:11 AM, Greg KH wrote:
> > On Mon, Oct 29, 2012 at 12:30:55PM +0800, zwu.ker...@gmail.com wrote:
> >> From: Zhi Yong Wu
> >>
> >> The debugfs function is used to get e
On Mon, Oct 29, 2012 at 12:30:55PM +0800, zwu.ker...@gmail.com wrote:
> From: Zhi Yong Wu
>
> The debugfs function is used to get expected dentry.
Huh? Why do you need this? Why haven't you added documentation for the
function saying what it does?
confused,
greg k-h
--
To unsubscribe from
On Mon, Oct 29, 2012 at 12:30:57PM +0800, zwu.ker...@gmail.com wrote:
> From: Zhi Yong Wu
>
> Add two proc files hot-kick-time and hot-update-delay
> under the dir /proc/sys/fs/ in order to turn
> TIME_TO_KICK and HEAT_UPDATE_DELAY into be tunable.
As you say, these are proc files, not sysfs f
On Fri, Apr 13, 2012 at 04:58:15PM +0200, Jan Schmidt wrote:
> commit 7a3ae2f8c8c8432e65467b7fc84d5deab04061a0 upstream.
>
> In commit 4692cf58 (Linux 3.3) we introduced new backref walking code for
> btrfs. This assumes we're searching live roots, which requires a transaction
> context. While scr
On Fri, Jun 03, 2011 at 01:10:49PM +0200, David Sterba wrote:
> On Wed, Jun 01, 2011 at 10:16:48AM -0500, Mitch Harder wrote:
> > I've been playing around with resurrecting the basic sysfs
> > capabilities that had been previously incorporated into btrfs.
> >
> > As it stands right now, it was rel
On Fri, Sep 24, 2010 at 08:39:41PM +0200, Jens Axboe wrote:
> On 2010-09-23 22:53, Greg KH wrote:
> > On Thu, Sep 23, 2010 at 09:40:14PM +0200, Jens Axboe wrote:
> >> On 2010-09-23 21:38, Andrew Morton wrote:
> >>>
> >>> (Cc sta...@kernel.org)
>
On Thu, Sep 23, 2010 at 09:40:14PM +0200, Jens Axboe wrote:
> On 2010-09-23 21:38, Andrew Morton wrote:
> >
> > (Cc sta...@kernel.org)
> >
> > On Wed, 22 Sep 2010 21:54:30 -0300
> > Cesar Eduardo Barros wrote:
> >
> >> This started appearing for me on v2.6.36-rc5-49-gc79bd89; it did not
> >> h
2.6.32-stable review patch. If anyone has any objections, please let us know.
--
From: Jiri Slaby
commit 2423fdfb96e3f9ff3baeb6c4c78d74145547891d upstream.
Stanse found 2 memory leaks in relocate_block_group and
__btrfs_map_block. cluster and multi are not freed/assigned on al
2.6.29-stable review patch. If anyone has any objections, please let us know.
--
From: Josef Bacik
commit df3935ffd6166fdd00702cf548fb5bb55737758b upstream.
Fix a problem where the generic block based fiemap stuff would not
properly set FIEMAP_EXTENT_LAST on the last extent.
58 matches
Mail list logo
