From: Robbie Harwood <rharwood@redhat.com>
To: Steve McIntyre <steve@einval.com>, grub-devel@gnu.org
Cc: 1021846@bugs.debian.org, programmer11180@programist.ru,
Sudhakar Kuppusamy <sudhakar@linux.ibm.com>
Subject: Re: [programmer11180@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]
Date: Mon, 28 Nov 2022 13:57:46 -0500 [thread overview]
Message-ID: <jlgmt8a3o0l.fsf@redhat.com> (raw)
In-Reply-To: <20221115183132.GJ3245702@tack.einval.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
Steve McIntyre <steve@einval.com> writes:
> Hi all!
>
> программист некто (in CC) reported this bug a few weeks back in
> Debian. Since I applied the bundle of filesystem bounds-checking fixes
> a few months back, he can't run grub-install. He's done the work to
> determine that the patch that breaks things for him is
>
> 2d014248d540c7e087934a94b6e7a2aa7fc2c704 fs/f2fs: Do not read past the end of nat journal entries
>
> The full thread of our discussion is at https://bugs.debian.org/1021846
>
> I don't have any knowledge of f2fs to go any further here. Help please! :-)
I don't know much about f2fs either, but has the value of `n` been
captured versus NAT_JOURNAL_ENTRIES in the failing case? Might be
useful to know how much it's going over by.
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-11-28 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 18:31 [programmer11180@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem] Steve McIntyre
2022-11-24 15:09 ` Daniel Kiper
2022-11-25 5:22 ` sudhakar
2022-11-25 18:04 ` Steve McIntyre
2022-11-28 18:57 ` Robbie Harwood [this message]
2022-12-02 14:41 ` Daniel Axtens
2022-12-03 17:43 ` Steve McIntyre
2022-12-04 19:46 ` программист некто
2022-12-09 7:17 ` Christian Hesse
-- strict thread matches above, loose matches on Subject: below --
2022-12-10 4:40 программист некто
2022-12-12 0:11 ` Steve McIntyre
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=jlgmt8a3o0l.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=1021846@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=programmer11180@programist.ru \
--cc=steve@einval.com \
--cc=sudhakar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.