All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/2] zonefs: prevent use of seq files as swap file
Date: Mon, 15 Mar 2021 07:23:30 +0000	[thread overview]
Message-ID: <BL0PR04MB651408289E9CB93DBB09334CE76C9@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: PH0PR04MB7416B66AA60FAAE2B48CCEBA9B6C9@PH0PR04MB7416.namprd04.prod.outlook.com

On 2021/03/15 15:46, Johannes Thumshirn wrote:
> On 15/03/2021 04:49, Damien Le Moal wrote:
>> The sequential write constraint of sequential zone file prevent their
>> use as swap files. Only allow conventional zone files to be used as swap
>> files.
> 
> That would be super useful to test in in zonefs tests as well. I can take
> care if you want.

Yep. Adding a test case for that.

> 
> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> 


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2021-03-15  7:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15  3:49 [PATCH 0/2] zonefs fixes Damien Le Moal
2021-03-15  3:49 ` [PATCH 1/2] zonefs: prevent use of seq files as swap file Damien Le Moal
2021-03-15  6:46   ` Johannes Thumshirn
2021-03-15  7:23     ` Damien Le Moal [this message]
2021-03-15  3:49 ` [PATCH 2/2] zonefs: Fix O_APPEND async write handling Damien Le Moal
2021-03-15  7:14   ` Johannes Thumshirn
2021-03-15  7:15   ` kernel test robot
2021-03-15  7:15     ` kernel test robot
2021-03-15  7:21     ` Johannes Thumshirn
2021-03-15  7:21     ` Johannes Thumshirn
2021-03-15  7:22       ` Damien Le Moal
2021-03-15  7:22       ` Damien Le Moal
2021-03-15 17:08         ` Nathan Chancellor
2021-03-15 17:08           ` Nathan Chancellor
2021-03-16  1:11           ` Damien Le Moal
2021-03-16  1:11           ` Damien Le Moal

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=BL0PR04MB651408289E9CB93DBB09334CE76C9@BL0PR04MB6514.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=linux-fsdevel@vger.kernel.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.