From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vadim Fedorenko <vadfed@meta.com>
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Jiri Slaby <jirislaby@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2 1/2] ptp: ocp: adjust sysfs entries to expose tty information
Date: Tue, 13 Aug 2024 11:33:47 +0200 [thread overview]
Message-ID: <2024081350-tingly-coming-a74d@gregkh> (raw)
In-Reply-To: <20240805220500.1808797-1-vadfed@meta.com>
On Mon, Aug 05, 2024 at 03:04:59PM -0700, Vadim Fedorenko wrote:
> Starting v6.8 the serial port subsystem changed the hierarchy of devices
> and symlinks are not working anymore. Previous discussion made it clear
> that the idea of symlinks for tty devices was wrong by design. Implement
> additional attributes to expose the information. Fixes tag points to the
> commit which introduced the change.
>
> Fixes: b286f4e87e32 ("serial: core: Move tty and serdev to be children of serial core port device")
> Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
> ---
> drivers/ptp/ptp_ocp.c | 68 +++++++++++++++++++++++++++++++++----------
> 1 file changed, 52 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/ptp/ptp_ocp.c b/drivers/ptp/ptp_ocp.c
> index ee2ced88ab34..7a5026656452 100644
> --- a/drivers/ptp/ptp_ocp.c
> +++ b/drivers/ptp/ptp_ocp.c
> @@ -3346,6 +3346,55 @@ static EXT_ATTR_RO(freq, frequency, 1);
> static EXT_ATTR_RO(freq, frequency, 2);
> static EXT_ATTR_RO(freq, frequency, 3);
>
> +static ssize_t
> +ptp_ocp_tty_show(struct device *dev, struct device_attribute *attr, char *buf)
> +{
> + struct dev_ext_attribute *ea = to_ext_attr(attr);
> + struct ptp_ocp *bp = dev_get_drvdata(dev);
> + struct ptp_ocp_serial_port *port;
> +
> + port = (void *)((uintptr_t)bp + (uintptr_t)ea->var);
That's insane pointer math, how do we know this is correct?
> + return sysfs_emit(buf, "ttyS%d", port->line);
> +}
> +
> +static umode_t
> +ptp_ocp_timecard_tty_is_visible(struct kobject *kobj, struct attribute *attr, int n)
> +{
> + struct ptp_ocp *bp = dev_get_drvdata(kobj_to_dev(kobj));
> + struct ptp_ocp_serial_port *port;
> + struct device_attribute *dattr;
> + struct dev_ext_attribute *ea;
> +
> + if (strncmp(attr->name, "tty", 3))
> + return attr->mode;
> +
> + dattr = container_of(attr, struct device_attribute, attr);
> + ea = container_of(dattr, struct dev_ext_attribute, attr);
> + port = (void *)((uintptr_t)bp + (uintptr_t)ea->var);
That's crazy pointer math, how are you ensured that it is correct? Why
isn't there a container_of() thing here instead?
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-13 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 22:04 [PATCH net v2 1/2] ptp: ocp: adjust sysfs entries to expose tty information Vadim Fedorenko
2024-08-05 22:05 ` [PATCH net v2 2/2] docs: ABI: update OCP TimeCard sysfs entries Vadim Fedorenko
2024-08-08 9:13 ` Simon Horman
2024-08-13 9:33 ` Greg Kroah-Hartman [this message]
2024-08-13 18:24 ` [PATCH net v2 1/2] ptp: ocp: adjust sysfs entries to expose tty information Vadim Fedorenko
2024-08-14 5:00 ` Jiri Slaby
2024-08-14 8:37 ` Vadim Fedorenko
2024-08-14 10:30 ` Jiri Slaby
2024-08-15 13:40 ` Vadim Fedorenko
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=2024081350-tingly-coming-a74d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vadfed@meta.com \
--cc=vadim.fedorenko@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).