Hello,
syzbot found the following issue on:
HEAD commit:66701750d556 Merge tag 'io_uring-6.16-20250630' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e4388c58
kernel config: https://syzkaller.appspot.com/x/.config?x=e29b8115bf337f53
das
On Fri, 4 Jul 2025 at 09:05, Eric Biggers wrote:
>
> Make fscrypt no longer use Crypto API drivers for non-inline crypto
> engines, even when the Crypto API prioritizes them over CPU-based code
> (which unfortunately it often does). These drivers tend to be really
> problematic, especially for fs
On Mon, 30 Jun 2025 at 19:24, Eric Biggers wrote:
>
> This series, including all its prerequisites, is also available at:
>
> git fetch
> https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git
> fsverity-libcrypto-v1
>
> This series makes fs/verity/ use the SHA-2 library API inst
On Fri 04-07-25 09:12:14, Qu Wenruo wrote:
> Currently all the filesystems implementing the
> super_opearations::shutdown() call back can not afford losing a device.
>
> Thus fs_bdev_mark_dead() will just call the shutdown() callback for the
> involved filesystem.
>
> But it will no longer be the
On Fri, 04 Jul 2025 10:12:29 +0930, Qu Wenruo wrote:
> Currently all the filesystems implementing the
> super_opearations::shutdown() callback can not afford losing a device.
>
> Thus fs_bdev_mark_dead() will just call the shutdown() callback for the
> involved filesystem.
>
> But it will no long
OK, now that you've made me read the changelog :) :
On Fri 04-07-25 10:12:29, Qu Wenruo wrote:
> Currently all the filesystems implementing the
> super_opearations::shutdown() callback can not afford losing a device.
^^^ operations
> Thus fs_bdev_mark_dead() will just call the shutdown()
Make fscrypt no longer use Crypto API drivers for non-inline crypto
engines, even when the Crypto API prioritizes them over CPU-based code
(which unfortunately it often does). These drivers tend to be really
problematic, especially for fscrypt's workload. This commit has no
effect on inline crypt
Dzień dobry,
Czy jest możliwość nawiązania współpracy z Państwem?
Z chęcią porozmawiam z osobą zajmującą się działaniami związanymi ze sprzedażą.
Pomagamy skutecznie pozyskiwać nowych klientów.
Zapraszam do kontaktu.
Pozdrawiam
Dominik Lotka
___
L
On Thu, Jul 3, 2025 at 6:35 PM Christoph Hellwig wrote:
>
> On Wed, Jul 02, 2025 at 11:43:12AM -0700, Darrick J. Wong wrote:
> > > On a spinning disk, random IO bandwidth remains unchanged, while
> > > sequential
> > > IO performance declines. However, setting nr_wb_ctx = 1 via configurable
> > >
On Wed, Jul 02, 2025 at 07:02:04PM +0800, Chao Yu wrote:
> As f2fs changes to use new mount APIs, let's add a new testcase
> to check mount result for all f2fs supported mount options and
> their combinations, in order to detect any inconsistency during
> mount.
>
> Cc: Jaegeuk Kim
> Signed-off-b
(https://download.01.org/0day-ci/archive/20250704/20250704.t8n0otve-...@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project
6146a88f60492b520a36f8f8f3231e15f3cc6082)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20250704/20250704
As f2fs changes to use new mount APIs, let's add a new testcase
to check mount result for all f2fs supported mount options and
their combinations, in order to detect any inconsistency during
mount.
Cc: Jaegeuk Kim
Signed-off-by: Chao Yu
---
v2:
- allow to check mount options w/ zoned device
com
On Fri, Jul 04, 2025 at 07:48:18PM +0800, Chao Yu wrote:
> As f2fs changes to use new mount APIs, let's add a new testcase
> to check mount result for all f2fs supported mount options and
> their combinations, in order to detect any inconsistency during
> mount.
>
> Cc: Jaegeuk Kim
> Signed-off-b
13 matches
Mail list logo
