All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sreyan Chakravarty <sreyan32@gmail.com>
To: Community support for Fedora users 
	<users@lists.fedoraproject.org>,
	Chris Murphy <lists@colorremedies.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs swapfile - Not enough swap space for hibernation.
Date: Mon, 14 Dec 2020 15:57:42 +0530	[thread overview]
Message-ID: <CAMaziXtXAivsV=8XuPr6Vtbz2n_=_z=fmuOYgwex8-mbNaVSyA@mail.gmail.com> (raw)
In-Reply-To: <CAMaziXsy4-_5RpN4cxviLX+infRL7-4NmvCEWz_QDA-spfLmXg@mail.gmail.com>

On Mon, Dec 14, 2020 at 2:57 PM Sreyan Chakravarty <sreyan32@gmail.com> wrote:
>
> On Sun, Dec 13, 2020 at 3:23 AM Chris Murphy <lists@colorremedies.com> wrote:
> > You are in adventure land. So you're going on an adventure. If you
> > want it to just work, use a swap partition.
>
> To be clear my problem is not with swap files per se.
>
> It's a SELinux error. I was asking for help on how to configure
> SELinux so it does not stop systemd-logind from accessing the
> /var/swap directory.
>
> It has nothing to do with swaps.
>
> FYI, I have used swaps in BTRFS with successful hibernation, but it
> fell apart when I restored snapshots.
>
> So I am not sure why you say a separate helper service will be required.
>

Done.

Changing to the "etc_runtime_t" solved problems.

But I am not sure if the permissions are not too permissive or not.

I have opened a discussion for that in Github:
https://github.com/fedora-selinux/selinux-policy/issues/508

-- 
Regards,
Sreyan Chakravarty

  reply	other threads:[~2020-12-14 10:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 11:28 btrfs swapfile - Not enough swap space for hibernation Sreyan Chakravarty
2020-12-10 19:02 ` Chris Murphy
2020-12-11 14:02   ` Sreyan Chakravarty
2020-12-12 21:52     ` Chris Murphy
2020-12-14  9:27       ` Sreyan Chakravarty
2020-12-14 10:27         ` Sreyan Chakravarty [this message]
2020-12-11 14:56   ` Sreyan Chakravarty
2020-12-11 15:15     ` Sreyan Chakravarty

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='CAMaziXtXAivsV=8XuPr6Vtbz2n_=_z=fmuOYgwex8-mbNaVSyA@mail.gmail.com' \
    --to=sreyan32@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=users@lists.fedoraproject.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.