Re: [PATCH v2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Scott Bauer <scott.bauer@xxxxxxxxx>
Subject: Re: [PATCH v2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 8 Feb 2017 23:18:19 -0800
Cc: linux-nvme@xxxxxxxxxxxxxxxxxxx, axboe@xxxxxx, keith.busch@xxxxxxxxx, jonathan.derrick@xxxxxxxxx, hch@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx
In-reply-to: <1486594815-2427-1-git-send-email-scott.bauer@intel.com>
User-agent: Mutt/1.7.1 (2016-10-04)

I'm really not a fan of adding a global synchronization point for
no good reason.  Arnd's original patch looks fine to me, but if you
really don't want it I'd suggest to use memdup_user and just
dynamically allocate the structure.

References:
- [PATCH v2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN
  - From: Scott Bauer

Prev by Date: RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
Next by Date: rate-capped fio jobs in a CFQ group degrade performance of fio jobs in another CFQ group with the same weight
Previous by thread: [PATCH v2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN
Next by thread: [PATCH] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux