Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13146] raspberrypi3_defconfig: "Inappropriate ioctl for device" almost at end when sdcard.img is created
Date: Mon, 10 Aug 2020 21:24:58 +0000	[thread overview]
Message-ID: <bug-13146-163-Bb6AJUM5t8@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13146-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=13146

--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
Does not happen here (openSUSE Tumbleweed, ext4 filesystem), which filesystem
do you use?

The fiemap feature was introduces lately in genimage (see [1]), and there is a
fallback in case the fiemap ioctl fails (see [2]):

        /* If failure is due to no filesystem support, return a single extent
*/
        if (ret == -EOPNOTSUPP)
                return whole_file_exent(size, extents, extent_count);

You can try to extend this check for ENOTTY (25) like the following:

        if (ret == -EOPNOTSUPP || ret == -ENOTTY)

or more correct (as 'ret = -errno;' some lines above):

        if (ret == EOPNOTSUPP || ret == ENOTTY)

and/or fallback to an earlier version of genimage in buildroot
by reverting the latest version bump commit [3]...

[1]
https://github.com/pengutronix/genimage/commit/1b98d6fadfca76cc0202a2df3debc67a8fe0ee1a
[2] https://github.com/pengutronix/genimage/blob/master/util.c#L390
[3]
https://git.buildroot.net/buildroot/commit/?id=677b0d9f574e2860cd22cb36022e5c059b4e6af5

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2020-08-10 21:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 19:08 [Buildroot] [Bug 13146] New: raspberrypi3_defconfig: "Inappropriate ioctl for device" almost at end when sdcard.img is created bugzilla at busybox.net
2020-08-10 21:24 ` bugzilla at busybox.net [this message]
2020-08-11  6:59 ` [Buildroot] [Bug 13146] " bugzilla at busybox.net
2020-08-11  7:24 ` bugzilla at busybox.net
2020-08-11  7:26 ` bugzilla at busybox.net
2020-08-11  7:38 ` bugzilla at busybox.net
2020-08-11 15:47 ` bugzilla at busybox.net
2020-08-11 16:58 ` bugzilla at busybox.net
2020-08-11 17:00 ` bugzilla at busybox.net
2020-08-11 19:27 ` bugzilla at busybox.net
2020-08-11 19:31 ` bugzilla at busybox.net
2020-08-11 19:33 ` bugzilla at busybox.net
2020-08-11 20:10 ` bugzilla at busybox.net
2020-08-11 20:14 ` bugzilla at busybox.net
2020-08-12 15:38 ` bugzilla at busybox.net
2020-08-12 19:23 ` bugzilla at busybox.net
2020-08-12 19:40 ` bugzilla at busybox.net

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=bug-13146-163-Bb6AJUM5t8@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.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