From: Dave Jones <davej@codemonkey.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: Linux 5.10
Date: Mon, 14 Dec 2020 00:31:47 -0500 [thread overview]
Message-ID: <20201214053147.GA24093@codemonkey.org.uk> (raw)
In-Reply-To: <CAHk-=whCKhxNyKn1Arut8xUDKTwp3fWcCj_jbL5dbzkUmo45gQ@mail.gmail.com>
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.
Dave
next prev parent reply other threads:[~2020-12-14 5:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 23:03 Linux 5.10 Linus Torvalds
2020-12-14 5:31 ` Dave Jones [this message]
2020-12-14 5:40 ` Dave Jones
2020-12-14 5:52 ` Greg KH
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=20201214053147.GA24093@codemonkey.org.uk \
--to=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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).