From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Jones <davej@codemonkey.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: Linux 5.10
Date: Mon, 14 Dec 2020 06:52:58 +0100
Message-ID: <X9b9ujh5T6U5+aBY@kroah.com> (raw)
In-Reply-To: <20201214053147.GA24093@codemonkey.org.uk>
On Mon, Dec 14, 2020 at 12:31:47AM -0500, Dave Jones wrote:
> On Sun, Dec 13, 2020 at 03:03:29PM -0800, Linus Torvalds wrote:
> > Ok, here it is - 5.10 is tagged and pushed out.
> >
> > I pretty much always wish that the last week was even calmer than it
> > was, and that's true here too. There's a fair amount of fixes in here,
> > including a few last-minute reverts for things that didn't get fixed,
> > but nothing makes me go "we need another week".
>
> ...
>
> > Mike Snitzer (1):
> > md: change mddev 'chunk_sectors' from int to unsigned
>
> Seems to be broken. This breaks mounting my raid6 partition:
>
> [ 87.290698] attempt to access beyond end of device
> md0: rw=4096, want=13996467328, limit=6261202944
> [ 87.293371] attempt to access beyond end of device
> md0: rw=4096, want=13998564480, limit=6261202944
> [ 87.296045] BTRFS warning (device md0): couldn't read tree root
> [ 87.300056] BTRFS error (device md0): open_ctree failed
>
> Reverting it goes back to the -rc7 behaviour where it mounts fine.
If the developer/maintainer(s) agree, I can revert this and push out a
5.10.1, just let me know.
thanks,
greg k-h
next prev parent reply index
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 23:03 Linus Torvalds
2020-12-14 5:31 ` Dave Jones
2020-12-14 5:40 ` Dave Jones
2020-12-14 5:52 ` Greg KH [this message]
2020-12-14 16:02 ` Mike Snitzer
2020-12-14 16:26 ` Mike Snitzer
2020-12-14 17:21 ` Jens Axboe
2020-12-14 17:29 ` Dave Jones
2020-12-14 16:44 ` Greg KH
2020-12-14 17:06 ` Mike Snitzer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X9b9ujh5T6U5+aBY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
LKML Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git
git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
linux-kernel@vger.kernel.org
public-inbox-index lkml
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git