Tag: btrfs

Linus Torvalds has just announced the release of Linux 5.1: So it’s a bit later in the day than I usually do this, just because I was waffling about the release. Partly because I got some small pull requests today, but mostly just because I wasn’t looking forward to the timing of this upcoming 5.2 merge window. But the last-minute pull requests really weren’t big enough to justify delaying things over, and hopefully the merge window timing won’t be all that painful either. I just happen to have the college graduation of my oldest happen right smack dab in the middle of the upcoming merge window, so I might be effectively offline for a few days there. If worst comes to worst, I’ll extend it to make it all work, but I don’t think it will be needed. Anyway, on to 5.1 itself. The past week has been pretty calm, and the final patch from rc6 is not all that …

Linus Torvalds has just released Linux 5.0: Ok, so the last week of the 5.0 release wasn’t entirely quiet, but it’s a lot smaller than rc8 was, and on the whole I’m happy that I delayed a week and did an rc8. It turns out that the actual patch that I talked about in the rc8 release wasn’t the worrisome bug I had thought: yes, we had an uninitialized variable, but the reason we hadn’t immediately noticed it due to a warning was that the way gcc works, the compiler had basically initialized it for us to the right value. So the same thing that caused not the lack of warning, also effectively meant that the fix was a no-op in practice. But hey, we had other bug fixes come in that actually did matter, and the uninitialized variable _could_ have been a problem with another compiler. Regardless – all is well that ends well. We have more than a …

Linus Torvalds released Linux Kernel 4.3 last week-end: So it *felt* like the last week of the rc series was busy, to the point where I got a bit worried about the release. But doing the actual numbers shows that that really was just my subjective feeling, probably due to the kernel summit and travel back home from Korea. It wasn’t actually a particularly busy week, it’s just that the pull requests were more noticeable in the last couple of days. We had a network update and a late fix for a x86 vm86 mode bug introduced by the vm86 cleanups, but other than that it’s just a collection of various small one-liners all over. Ok, the vm86 mode thing was a one-liner too, it was just slightly more nerve-wracking because it looked scarier than it was before people (Andy) figured out what was going on. The changes from rc7 are dominated by the network stuff, but as you can …

Linus Torvalds “Ima Sheep” released Linux Kernel 4.0 on Sunday: So I decided to release 4.0 as per the normal schedule, because there really weren’t any known issues, and while I’ll be traveling during the end of the upcoming week due to a college visit, I’m hoping that won’t affect the merge window very much. We’ll see. Linux 4.0 was a pretty small release both in linux-next and in final size, although obviously “small” is all relative. It’s still over 10k non-merge commits. But we’ve definitely had bigger releases (and judging by linux-next v4.1 is going to be one of the bigger ones). Which is all good. It definitely matches the “v4.0 is supposed to be a_stable_ release”, and very much not about new experimental features etc. I’m personally so much happier with time-based releases than the bad old days when we had feature-based releases. That said, there’s a few interesting numerological things going on with 4.0. Looking at just …

Linus Torvalds released Linux Kernel 3.19 yesterday: So nothing all that exciting happened, and while I was tempted a couple of times to do an rc8, there really wasn’t any reason for it. Just as an example, Sasha Levin used KASan and found an interesting bug in paravirtualized spinlocks, but realistically it’s been around forever, and it’s not even clear that it can really ever trigger in practice. We’ll get it fixed, and mark it for stable, and tempting as it was, it wasn’t really a reason to delay 3.19. And the actual fixes that went in (see appended shortlog) were all fairly small, with the exception of some medium-sized infiniband changes that were all reverting code that just wasn’t ready. So it’s out there – go and get it. And as a result, the merge window for 3.20 is obviously also now open. Linus Linux 3.18 improved performance of the network stack, received BTRFS and EXT-4 file systems improvements, …

Linus Torvalds released Linux Kernel 3.18 last Sunday: It’s been a quiet week, and the patch from rc7 is tiny, so 3.18 is out. I’d love to say that we’ve figured out the problem that plagues 3.17 for a couple of people, but we haven’t. At the same time, there’s absolutely no point in having everybody else twiddling their thumbs when a couple of people are actively trying to bisect an older issue, so holding up the release just didn’t make sense. Especially since that would just have then held things up entirely over the holiday break. So the merge window for 3.19 is open, and DaveJ will hopefully get his bisection done (or at least narrow things down sufficiently that we have that “Ahaa” moment) over the next week. But in solidarity with Dave (and to make my life easier too 😉 let’s try to avoid introducing any _new_ nasty issues, ok? Linus Linux 3.17 added support for Xbox …

Linus Torvalds announced the release of Linux Kernel 3.15 last Sunday: So I ended up doing an rc8 because I was a bit worried about some last-minute dcache fixes, but it turns out that nobody seemed to even notice those. We did have other issues during the week, though, so it was just as well. The futex fixes and cleanups may stand out, but as usual there’s various other random fixes since rc8 in there too: mainly drivers (drm, networking, sound, usb etc), networking, scheduling and perf tooling. But it’s all been fairly small and quiet, which *may* of course be due to the fact that last week was also the first week of the merge window for 3.16. That might have distracted some developers. I’m not entirely convinced I liked the overlap, but it seemed to work ok, and unless people scream really loudly (“Please don’t _ever_ do that again”) and give good reasons for doing so, I might end up doing that …

Linus Torvalds has announced the release of Linux Kernel 3.12: I was vacillating whether to do an rc8 or just cut the final 3.12, but since the biggest reason to *not* do a final release was not so much the state of the code, as simply the fact that I’ll be traveling with very bad internet connection next week, I didn’t really want to delay the release. Sure, we had a number of driver reverts, and there was an annoying auto-NUMA memory corruption fix series, but none of it was really worth delaying 3.12 for. But the fact that I’m going to be (effectively) off-line next week means that I’m *not* opening the merge window for 3.13 yet – since I won’t have the bandwidth to really do merges anyway. That doesn’t mean that you can’t send me pull request for the merge window early, of course – maintainers can *always* send their pull requests early rather than late, if …

Embedded Systems Jobs

Facebook is seeking a Software Engineer to design, develop and implement hardware-near software for accelerators and other components used in our infrastructure. This person will be an integral member of the team, responsible for embedded software de

We are a smart team of doers that work passionately to apply cutting-edge advances in and to solve real-world challenges that will transform our customers experiences in ways we cant even imagine yet. As a Firmware Engineer, you will be working with

Echo Frames is Amazon's first prescription-ready smart glasses. In this role, you will be working on the current and future roadmap for Echo Frames. The team is focused on bringing technology and design into a form that is familiar to millions of gla

Echo Frames is Amazon's first prescription-ready smart glasses. In this role, you will be working on the current and future roadmap for Echo Frames. The team is focused on bringing technology and design into a form that is familiar to millions of gla

RT-Thread was born in 2006, it is an open-source, neutral, and community-based real-time operating system. As an open-source project, RT-Thread has received strong support and contributions from the community developers and many chips and original eq