Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp438282pxt; Thu, 12 Aug 2021 01:54:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxeYj2VS3GpouEJauI++lnEhVL157mSWWT1No1oNv6MzSPPxvBVpuLE5lKbi6NNU0ZJUtai X-Received: by 2002:a17:906:1f8e:: with SMTP id t14mr2576246ejr.313.1628758462963; Thu, 12 Aug 2021 01:54:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628758462; cv=none; d=google.com; s=arc-20160816; b=uDVF8dEAY/Aj3L/Yije3KdaNoQ3rkS1tmE87Zgg2JwAG+gxGJMIsO+CHzp8VLb4YSf NdIwXxeD4bYKB+oSBbNRUw5L32SqcONJJxgkv9SZ+Gv90DC6rfVLgv0k9XC16GlwUUK3 OeWK+GhA7VETdHK4LFGOAp4rXe+P6S1niZK4eKTGX9iWdWb27onvR9Qw8wR3bYgoltMn hH8sISUmKgKF5aa8K47EvcuFkbnvFpYRCDzcX5X2z1z62s1vRgPvxUC3GK7M2Fw6yGG/ ydmQSD4Em0mG8sdGFt9t8+RKjOzcDaaCEZQ34XveQOcACflVkG7PoLzpicyT3KhwpPQS xoxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from; bh=EtPskSg58e++qbZAVWkYYEyVkZigEV1ohxM4dwzOIyA=; b=BA6W5JpMdMCRyxtZR9dA7REXU1fo4p0MAhSLbk/twFZCIiVlwN3B5Ok6WUQEg2xTRF lwkGXTOPC4WcA6grrTeC/HNHnI3iJOlyw94sp3WFN3UHqnSk46RV3u8PuwuNtxAahJmT OYEsTwzxSN90/bWEr0S6zKeI6XSnfc8dHc00UC42n0zS/iBrVlJcAs/46CWM6iML46oe uWkt81qOLfy3M9B83HogJUZv+OLse2JZlBcPfC3NEp95v43KvADPZzihItzjfrm493Ww nFdl6Jy0ZaIQ6Kq4fQi//1KUkajoPgG1hlWZLJ5xnXYKw99qi30Na0mG+EMUk89iXLCY DDUg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ec28si2023704edb.143.2021.08.12.01.53.59; Thu, 12 Aug 2021 01:54:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235420AbhHLIvx (ORCPT + 99 others); Thu, 12 Aug 2021 04:51:53 -0400 Received: from out4436.biz.mail.alibaba.com ([47.88.44.36]:52165 "EHLO out4436.biz.mail.alibaba.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235302AbhHLIvw (ORCPT ); Thu, 12 Aug 2021 04:51:52 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R721e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04420;MF=xianting.tian@linux.alibaba.com;NM=1;PH=DS;RN=10;SR=0;TI=SMTPD_---0Uilubck_1628758275; Received: from localhost(mailfrom:xianting.tian@linux.alibaba.com fp:SMTPD_---0Uilubck_1628758275) by smtp.aliyun-inc.com(127.0.0.1); Thu, 12 Aug 2021 16:51:15 +0800 From: Xianting Tian To: gregkh@linuxfoundation.org, jirislaby@kernel.org, amit@kernel.org, arnd@arndb.de, osandov@fb.com Cc: linuxppc-dev@lists.ozlabs.org, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, guoren@kernel.org, Xianting Tian Subject: [PATCH v5 1/2] tty: hvc: pass DMA capable memory to put_chars() Date: Thu, 12 Aug 2021 16:51:11 +0800 Message-Id: <20210812085112.145265-2-xianting.tian@linux.alibaba.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20210812085112.145265-1-xianting.tian@linux.alibaba.com> References: <20210812085112.145265-1-xianting.tian@linux.alibaba.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As well known, hvc backend can register its opertions to hvc backend. the opertions contain put_chars(), get_chars() and so on. Some hvc backend may do dma in its opertions. eg, put_chars() of virtio-console. But in the code of hvc framework, it may pass DMA incapable memory to put_chars() under a specific configuration, which is explained in commit c4baad5029(virtio-console: avoid DMA from stack): 1, c[] is on stack, hvc_console_print(): char c[N_OUTBUF] __ALIGNED__; cons_ops[index]->put_chars(vtermnos[index], c, i); 2, ch is on stack, static void hvc_poll_put_char(,,char ch) { struct tty_struct *tty = driver->ttys[0]; struct hvc_struct *hp = tty->driver_data; int n; do { n = hp->ops->put_chars(hp->vtermno, &ch, 1); } while (n <= 0); } Commit c4baad5029 is just the fix to avoid DMA from stack memory, which is passed to virtio-console by hvc framework in above code. But I think the fix is aggressive, it directly uses kmemdup() to alloc new buffer from kmalloc area and do memcpy no matter the memory is in kmalloc area or not. But most importantly, it should better be fixed in the hvc framework, by changing it to never pass stack memory to the put_chars() function in the first place. Otherwise, we still face the same issue if a new hvc backend using dma added in the furture. We make 'char c[N_OUTBUF]' part of 'struct hvc_struct', so hp->c is no longer the stack memory. we can use it in above two cases. Other cleanup is use ARCH_DMA_MINALIGN for align, and make 'hp->outbuf' aligned and use struct_size() for the size parameter of kzalloc(). With the patch, we can remove the fix c4baad5029. Signed-off-by: Xianting Tian Tested-by: Xianting Tian --- drivers/tty/hvc/hvc_console.c | 40 +++++++++++++++++++++-------------- drivers/tty/hvc/hvc_console.h | 16 ++++++++++++-- 2 files changed, 38 insertions(+), 18 deletions(-) diff --git a/drivers/tty/hvc/hvc_console.c b/drivers/tty/hvc/hvc_console.c index 5bb8c4e44..c56564eb7 100644 --- a/drivers/tty/hvc/hvc_console.c +++ b/drivers/tty/hvc/hvc_console.c @@ -41,16 +41,6 @@ */ #define HVC_CLOSE_WAIT (HZ/100) /* 1/10 of a second */ -/* - * These sizes are most efficient for vio, because they are the - * native transfer size. We could make them selectable in the - * future to better deal with backends that want other buffer sizes. - */ -#define N_OUTBUF 16 -#define N_INBUF 16 - -#define __ALIGNED__ __attribute__((__aligned__(sizeof(long)))) - static struct tty_driver *hvc_driver; static struct task_struct *hvc_task; @@ -142,6 +132,7 @@ static int hvc_flush(struct hvc_struct *hp) static const struct hv_ops *cons_ops[MAX_NR_HVC_CONSOLES]; static uint32_t vtermnos[MAX_NR_HVC_CONSOLES] = {[0 ... MAX_NR_HVC_CONSOLES - 1] = -1}; +static char *cons_outbuf[MAX_NR_HVC_CONSOLES]; /* * Console APIs, NOT TTY. These APIs are available immediately when @@ -151,18 +142,23 @@ static uint32_t vtermnos[MAX_NR_HVC_CONSOLES] = static void hvc_console_print(struct console *co, const char *b, unsigned count) { - char c[N_OUTBUF] __ALIGNED__; + char *c; unsigned i = 0, n = 0; int r, donecr = 0, index = co->index; + unsigned long flags; + struct hvc_struct *hp; /* Console access attempt outside of acceptable console range. */ if (index >= MAX_NR_HVC_CONSOLES) return; /* This console adapter was removed so it is not usable. */ - if (vtermnos[index] == -1) + if (vtermnos[index] == -1 || !cons_outbuf[index]) return; + c = cons_outbuf[index]; + + spin_lock_irqsave(&hp->c_lock, flags); while (count > 0 || i > 0) { if (count > 0 && i < sizeof(c)) { if (b[n] == '\n' && !donecr) { @@ -191,6 +187,7 @@ static void hvc_console_print(struct console *co, const char *b, } } } + spin_unlock_irqrestore(&hp->c_lock, flags); hvc_console_flush(cons_ops[index], vtermnos[index]); } @@ -878,9 +875,19 @@ static void hvc_poll_put_char(struct tty_driver *driver, int line, char ch) struct tty_struct *tty = driver->ttys[0]; struct hvc_struct *hp = tty->driver_data; int n; + unsigned long flags; + char *c; + + if (!hp || !cons_outbuf[hp->index]) + return; + + c = cons_outbuf[hp->index]; do { - n = hp->ops->put_chars(hp->vtermno, &ch, 1); + spin_lock_irqsave(&hp->c_lock, flags); + c[0] = ch; + n = hp->ops->put_chars(hp->vtermno, c, 1); + spin_unlock_irqrestore(&hp->c_lock, flags); } while (n <= 0); } #endif @@ -922,8 +929,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data, return ERR_PTR(err); } - hp = kzalloc(ALIGN(sizeof(*hp), sizeof(long)) + outbuf_size, - GFP_KERNEL); + hp = kzalloc(struct_size(hp, outbuf, outbuf_size), GFP_KERNEL); if (!hp) return ERR_PTR(-ENOMEM); @@ -931,13 +937,13 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data, hp->data = data; hp->ops = ops; hp->outbuf_size = outbuf_size; - hp->outbuf = &((char *)hp)[ALIGN(sizeof(*hp), sizeof(long))]; tty_port_init(&hp->port); hp->port.ops = &hvc_port_ops; INIT_WORK(&hp->tty_resize, hvc_set_winsz); spin_lock_init(&hp->lock); + spin_lock_init(&hp->c_lock); mutex_lock(&hvc_structs_mutex); /* @@ -964,6 +970,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtermno, int data, if (i < MAX_NR_HVC_CONSOLES) { cons_ops[i] = ops; vtermnos[i] = vtermno; + cons_outbuf[i] = hp->c; } list_add_tail(&(hp->next), &hvc_structs); @@ -988,6 +995,7 @@ int hvc_remove(struct hvc_struct *hp) if (hp->index < MAX_NR_HVC_CONSOLES) { vtermnos[hp->index] = -1; cons_ops[hp->index] = NULL; + cons_outbuf[hp->index] = NULL; } /* Don't whack hp->irq because tty_hangup() will need to free the irq. */ diff --git a/drivers/tty/hvc/hvc_console.h b/drivers/tty/hvc/hvc_console.h index 18d005814..52374e2da 100644 --- a/drivers/tty/hvc/hvc_console.h +++ b/drivers/tty/hvc/hvc_console.h @@ -32,13 +32,21 @@ */ #define HVC_ALLOC_TTY_ADAPTERS 8 +/* + * These sizes are most efficient for vio, because they are the + * native transfer size. We could make them selectable in the + * future to better deal with backends that want other buffer sizes. + */ +#define N_OUTBUF 16 +#define N_INBUF 16 + +#define __ALIGNED__ __attribute__((__aligned__(sizeof(long)))) + struct hvc_struct { struct tty_port port; spinlock_t lock; int index; int do_wakeup; - char *outbuf; - int outbuf_size; int n_outbuf; uint32_t vtermno; const struct hv_ops *ops; @@ -48,6 +56,10 @@ struct hvc_struct { struct work_struct tty_resize; struct list_head next; unsigned long flags; + spinlock_t c_lock; + char c[N_OUTBUF] __ALIGNED__; + int outbuf_size; + char outbuf[0] __ALIGNED__; }; /* implemented by a low level driver */ -- 2.17.1