public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Christian Brauner <brauner@kernel.org>
Cc: Ziran Zhang <zhangcoder@yeah.net>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4] FAT: Allow 0xE9 near jump in fat_read_static_bpb()
Date: Sun, 12 Apr 2026 16:37:48 +0900	[thread overview]
Message-ID: <87se90ljcj.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20260412070109.5197-1-zhangcoder@yeah.net>

Ziran Zhang <zhangcoder@yeah.net> writes:

> The fat_read_static_bpb() only accepts a short jump as a valid
> bootstrap code signature for DOS 1.x volumes when the dos1xfloppy
> mount option is used.
>
> However, according to the Microsoft fatgen103.doc, the BS_jmpBoot
> field has two allowed forms: 0xEB 0x?? 0x90 (short jump + NOP)
> and 0xE9 0x?? 0x?? (near jump). The specification explicitly states
> that either form is acceptable.
>
> This patch relaxes the check to also accept 0xE9 as the first byte of
> the jump instruction.
>
> Changes in v4:
> - Add original commit log
>
> Signed-off-by: Ziran Zhang <zhangcoder@yeah.net>

Thanks.

Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

> ---
>
>> Could you add original commit log, instead of changelog?
>> 
>> Thanks.
>
> Done! Please ignore the earlier erroneous v2 v2 and v3.
>
>  fs/fat/inode.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fat/inode.c b/fs/fat/inode.c
> index 28f78df08..0e7d106ea 100644
> --- a/fs/fat/inode.c
> +++ b/fs/fat/inode.c
> @@ -1479,8 +1479,9 @@ static int fat_read_static_bpb(struct super_block *sb,
>  	int error = -EINVAL;
>  	unsigned i;
>  
> -	/* 16-bit DOS 1.x reliably wrote bootstrap short-jmp code */
> -	if (b->ignored[0] != 0xeb || b->ignored[2] != 0x90) {
> +	/* 16-bit DOS 1.x reliably wrote bootstrap short-jmp or near-jmp code */
> +	if ((b->ignored[0] != 0xeb || b->ignored[2] != 0x90) &&
> +	    (b->ignored[0] != 0xe9)) {
>  		if (!silent)
>  			fat_msg(sb, KERN_ERR,
>  				"%s; no bootstrapping code", notdos1x);

-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

      reply	other threads:[~2026-04-12  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11  8:01 [PATCH] FAT: Allow 0xE9 near jump in fat_read_static_bpb() Ziran Zhang
2026-04-11 17:32 ` OGAWA Hirofumi
2026-04-12  1:39   ` [PATCH v2 v2] " Ziran Zhang
2026-04-12  3:56     ` [PATCH v3] " Ziran Zhang
2026-04-12  6:21       ` OGAWA Hirofumi
2026-04-12  6:59         ` [PATCH v4] " Ziran Zhang
2026-04-12  7:37           ` OGAWA Hirofumi [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=87se90ljcj.fsf@mail.parknet.co.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhangcoder@yeah.net \
    /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