All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Ronald Wahl <ronald.wahl@raritan.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
	Mark Brown <broonie@kernel.org>,
	 linux-spi <linux-spi@vger.kernel.org>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Ryan Wanner <ryan.wanner@microchip.com>,
	 stable <stable@vger.kernel.org>,
	 Richard Weinberger <richard.weinberger@gmail.com>,
	 David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 1/2] spi: atmel: Do not cancel a transfer upon any signal
Date: Thu, 30 Nov 2023 21:58:37 +0100 (CET)	[thread overview]
Message-ID: <1578539475.50621.1701377917637.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <d4ffca97-bb5d-4c42-a025-69b308c24f82@raritan.com>

----- Ursprüngliche Mail -----
> Von: "Ronald Wahl" <ronald.wahl@raritan.com>
> I think yes. But the only thing the FS can do is stop any writes from now
> on which is not a useful consequence of killing a process.

Exactly. If I understand the spi code correctly, now an *unprivileged*
user can abort a file operation on UBIFS and UBIFS will switch to read-only mode.
...which is pretty bad.

Thanks,
//richard

  reply	other threads:[~2023-11-30 20:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  9:58 [PATCH 1/2] spi: atmel: Do not cancel a transfer upon any signal Miquel Raynal
2023-11-27  9:58 ` [PATCH 2/2] spi: atmel: Drop unused defines Miquel Raynal
2023-11-27 15:10 ` [PATCH 1/2] spi: atmel: Do not cancel a transfer upon any signal Ronald Wahl
2023-11-27 17:54   ` Ronald Wahl
2023-11-29  8:49     ` Miquel Raynal
2023-11-29 11:05       ` Ronald Wahl
2023-11-30 12:46       ` Richard Weinberger
2023-11-30 18:26         ` Richard Weinberger
2023-11-30 18:36           ` Ronald Wahl
2023-11-30 20:15           ` Miquel Raynal
2023-11-30 20:43             ` Ronald Wahl
2023-11-30 20:58               ` Richard Weinberger [this message]
2023-12-01 11:13               ` David Laight
2023-12-01 13:38                 ` Ronald Wahl
2023-12-04 11:54                   ` Ronald Wahl
2023-12-04 12:26                     ` Mark Brown
2023-12-04 12:39                       ` Ronald Wahl
2023-12-04 12:19                   ` David Laight
2023-12-05  7:49               ` Miquel Raynal
2023-11-27 16:48 ` Mark Brown
2023-12-01 14:16 ` Mark Brown
2023-12-04 15:47 ` Mark Brown

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=1578539475.50621.1701377917637.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=broonie@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard.weinberger@gmail.com \
    --cc=ronald.wahl@raritan.com \
    --cc=ryan.wanner@microchip.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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 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.