From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
Cc: "Schmidl, Tobias" <tobiasschmidl@siemens.com>,
isar-users@googlegroups.com, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/1] expand last partition supports btrfs (inline test)
Date: Fri, 30 Sep 2022 13:17:44 +0200 [thread overview]
Message-ID: <CAJGKYO77tc2S+JhYwaOXLJsRjCw45e66ZSB5VeLNFim3=s0PcA@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO61sMuQie9fJ8W76+L2kD2vQ7Yzkiwc_bvBczxegdr-VA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Il Ven 30 Set 2022, 13:09 Roberto A. Foglietta <roberto.foglietta@gmail.com>
ha scritto:
>
> Third: The mount point (/tmp/btrfs) is never cleaned up in the Robertos
>> patch.
>>
>
> I do umount but NOT rmdir because if for some reason umount fails
> (expecially in combination with a bug that do not let the error code be
> returned, I saw in busybox) I am going to remove the filesystem content.
> Moreover, polluting the /tmp is usually not an issue.
>
Two toughts ecollided in my head:
1. do not run rm -rf on a dir that can contain a umounted filesystem
2. just in case do rmdir that will fail and do not harm the content
The result was quite curios: I the doubt I do not do anything but
polluting /tmp!
>
[-- Attachment #2: Type: text/html, Size: 1575 bytes --]
next prev parent reply other threads:[~2022-09-30 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 8:00 Roberto A. Foglietta
2022-09-30 8:56 ` Jan Kiszka
2022-09-30 10:23 ` Schmidl, Tobias
2022-09-30 10:39 ` Roberto A. Foglietta
2022-09-30 10:50 ` Bezdeka, Florian
2022-09-30 11:09 ` Roberto A. Foglietta
2022-09-30 11:17 ` Roberto A. Foglietta [this message]
2022-09-30 10:51 ` Henning Schild
2022-09-30 11:34 ` Fwd: [PATCH 1/1] expand last partition supports btrfs (inline 2nd version) Roberto A. Foglietta
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='CAJGKYO77tc2S+JhYwaOXLJsRjCw45e66ZSB5VeLNFim3=s0PcA@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=tobiasschmidl@siemens.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