From: Matthew Wilcox <willy@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: reiserfs-devel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org,
butt3rflyh4ck <butterflyhuangxx@gmail.com>
Subject: Re: [PATCH] reiserfs: Check the return value from __getblk()
Date: Tue, 4 Jul 2023 19:49:24 +0100 [thread overview]
Message-ID: <ZKRptMjtL6X74X1B@casper.infradead.org> (raw)
In-Reply-To: <20230630-kerbholz-koiteich-a7395bc04eae@brauner>
On Fri, Jun 30, 2023 at 11:03:05AM +0200, Christian Brauner wrote:
> From: Matthew Wilcox <willy@infradead.org>
>
> On Thu, 29 Jun 2023 23:26:17 +0200, Matthew Wilcox wrote:
> > __getblk() can return a NULL pointer if we run out of memory or if
> > we try to access beyond the end of the device; check it and handle it
> > appropriately.
> >
> > [...]
>
> Willy's original commit with message id
> <20230605142335.2883264-1-willy@infradead.org> didn't show up on lore.
> Might be because reiserfs-devel isn't a list tracked by lore; not sure.
> So I grabbed this from somewhere else.
>
> In any case, I picked this up now.
>
> ---
>
> Applied to the vfs.misc branch of the vfs/vfs.git tree.
> Patches in the vfs.misc branch should appear in linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
Acked-by: Edward Shishkin <edward.shishkin@gmail.com>
was added in a response to the original, FYI
next prev parent reply other threads:[~2023-07-04 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230605142335.2883264-1-willy@infradead.org>
2023-06-29 21:26 ` [PATCH] reiserfs: Check the return value from __getblk() Matthew Wilcox
2023-06-30 9:03 ` Christian Brauner
2023-07-04 18:49 ` Matthew Wilcox [this message]
2023-07-05 7:08 ` Christian Brauner
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=ZKRptMjtL6X74X1B@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=butterflyhuangxx@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.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).