From: Alan Huang <mmpgouride@gmail.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org,
syzbot+d10151bf01574a09a915@syzkaller.appspotmail.com
Subject: Re: [PATCH] bcachefs: Add missing error handling
Date: Sun, 13 Apr 2025 22:24:10 +0800 [thread overview]
Message-ID: <922FBCAC-0C64-4712-9017-BAE5F8E61FF8@gmail.com> (raw)
In-Reply-To: <tjbg7uavlujkxoijtfagmbl7sdewnzgsgo4jmlghoywwgd7vum@d7vbnrrm7dtq>
On Apr 13, 2025, at 17:59, Kent Overstreet <kent.overstreet@linux.dev> wrote:
>
> On Sat, Apr 12, 2025 at 06:20:49PM +0800, Alan Huang wrote:
>> Reported-by: syzbot+d10151bf01574a09a915@syzkaller.appspotmail.com
>> Signed-off-by: Alan Huang <mmpgouride@gmail.com>
>
> This was a silly mistake.
>
> In the past I've thought about going through and marking huge swaths of
> functions as __must_check, maybe that would actually be worth doing?
Yeah, that’s a good idea.
>
>> ---
>> fs/bcachefs/recovery.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/bcachefs/recovery.c b/fs/bcachefs/recovery.c
>> index d2b07f602da9..606d684e6f23 100644
>> --- a/fs/bcachefs/recovery.c
>> +++ b/fs/bcachefs/recovery.c
>> @@ -1125,7 +1125,10 @@ int bch2_fs_initialize(struct bch_fs *c)
>> * journal_res_get() will crash if called before this has
>> * set up the journal.pin FIFO and journal.cur pointer:
>> */
>> - bch2_fs_journal_start(&c->journal, 1);
>> + ret = bch2_fs_journal_start(&c->journal, 1);
>> + if (ret)
>> + goto err;
>> +
>> set_bit(BCH_FS_accounting_replay_done, &c->flags);
>> bch2_journal_set_replay_done(&c->journal);
>>
>> --
>> 2.48.1
>>
prev parent reply other threads:[~2025-04-13 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 10:20 [PATCH] bcachefs: Add missing error handling Alan Huang
2025-04-13 9:59 ` Kent Overstreet
2025-04-13 14:24 ` Alan Huang [this message]
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=922FBCAC-0C64-4712-9017-BAE5F8E61FF8@gmail.com \
--to=mmpgouride@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=syzbot+d10151bf01574a09a915@syzkaller.appspotmail.com \
/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