On Mon, Jan 23, 2023 at 10:59:45AM -0800, Andrew Morton wrote:
> On Sun, 22 Jan 2023 08:20:06 +0100 Christoph Hellwig wrote:
>
> > On Sat, Jan 21, 2023 at 05:06:41PM -0800, Andrew Morton wrote:
> > > This patchset doesn't apply to fs/btrfs/ because linux-next contains
> > > this 6+ month-old comm
On Sun, 22 Jan 2023 08:20:06 +0100 Christoph Hellwig wrote:
> On Sat, Jan 21, 2023 at 05:06:41PM -0800, Andrew Morton wrote:
> > This patchset doesn't apply to fs/btrfs/ because linux-next contains
> > this 6+ month-old commit:
>
> Hmm. It was literally written against linux-next as of last mor
On Mon, Jan 23, 2023 at 11:05:56AM +0100, Jan Kara wrote:
> Thanks for the heads up. So we had kind of a similar issue for ext4 but it
> got caught by Ted during his regression runs so we've basically done what
> GFS2 is doing for the merge window and now there's patchset pending to
> convert the d
On Sat, Jan 21, 2023 at 07:57:55AM +0100, Christoph Hellwig wrote:
> Instead of returning NULL for all errors, distinguish between:
>
> - no entry found and not asked to allocated (-ENOENT)
> - failed to allocate memory (-ENOMEM)
> - would block (-EAGAIN)
>
> so that callers don't have to gues
On Sun 22-01-23 12:05:53, Linus Torvalds wrote:
> On Sun, Jan 22, 2023 at 1:01 AM Andreas Gruenbacher
> wrote:
> >
> > gfs2 writepage fix
> >
> > - Fix a regression introduced by commit "gfs2: stop using
> > generic_writepages in gfs2_ail1_start_one".
>
> Hmm. I'm adding a few more people and
