All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] busybox: fix mount issue
Date: Wed, 17 Apr 2013 08:04:16 -0700	[thread overview]
Message-ID: <516EB9F0.6050301@linux.intel.com> (raw)
In-Reply-To: <1366206752-26309-1-git-send-email-laurentiu.palcu@intel.com>

On 04/17/2013 06:52 AM, Laurentiu Palcu wrote:
> When the mount command is not given the filesystem type to mount, then
> it will try all the known filesystems. However, when a filesystem is not
> supported by the kernel, the mount function call will return ENODEV.
>
> The following patch, ecd90bc6aa63da2aef2513ac090d4b426b2b719c,
> introduced a problem because it bailed out on ENODEV too. Instead it should
> have only bailed out on ENOMEDIUM.
>
> [YOCTO #4308]
>
> Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Acked-by & Tested-by: Saul Wold <sgw@linux.intel.com>


> ---
> Saul, Khem,
>
> Would you guys give this a test? Mounting should work just fine now and my
> tests didn't show any issues. I didn't test the 'fail on no media' case
> though... If you can quickly test this, it would be nice.
>
> Thanks,
> Laurentiu
>
>
>   .../busybox/busybox-1.20.2/fail_on_no_media.patch  |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/busybox/busybox-1.20.2/fail_on_no_media.patch b/meta/recipes-core/busybox/busybox-1.20.2/fail_on_no_media.patch
> index aa2cd25..6745f16 100644
> --- a/meta/recipes-core/busybox/busybox-1.20.2/fail_on_no_media.patch
> +++ b/meta/recipes-core/busybox/busybox-1.20.2/fail_on_no_media.patch
> @@ -23,7 +23,7 @@ Index: busybox-1.20.2/util-linux/mount.c
>   +		 * Break if there is no media, no point retrying for all
>   +		 * fs types since there is no media available
>   +		 */
> -+		if ((rc == -1) && (errno == ENOMEDIUM || errno == ENODEV)) {
> ++		if (rc == -1 && errno == ENOMEDIUM) {
>   +			bb_perror_msg_and_die("mounting %s on %s failed", mp->mnt_fsname, mp->mnt_dir);
>   +		}
>    		if (!rc || (vfsflags & MS_RDONLY) || (errno != EACCES && errno != EROFS))
>



      reply	other threads:[~2013-04-17 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 13:52 [PATCH] busybox: fix mount issue Laurentiu Palcu
2013-04-17 15:04 ` Saul Wold [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=516EB9F0.6050301@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=laurentiu.palcu@intel.com \
    --cc=openembedded-core@lists.openembedded.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 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.